-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option to create/navigate to a controller from ng-controller #20
Comments
This is similar to PR #11, which would add a reference between the value of the The second part, create from usage, isn't covered and will have to be a separate piece of work. How would you expect it to work - where would it create the controller? In the HTML file, or in a new file, alongside, or in the scripts folder? |
re: 2nd part I realise that's not everybody's preference, but the way I structure the code is having them side by side:
That would obviously be my preference. |
Is there a convention in angularjs world (I'm not familiar enough)? |
I'm not sure,,, haven't seen any strong guidance around that, but I'm quite new to Angular myself, and figuring it out as I go |
No it is not a convention. most from what i see put the view in seperate folders |
@citizenmatt i think on the weekend i can work in the plugin |
btw. the "other" guys uses often yeoman For an example of the structure look here. http://www.sitepoint.com/kickstart-your-angularjs-development-with-yeoman-grunt-and-bower/ |
Hi @DerAlbertCom - any movement on the PR? I'm going to need an ICache implementation soon. I'm happy if you just want to push what you've got. |
@citizenmatt my last work is on Some initial Cache implementation https://github.com/DerAlbertCom/resharper-angularjs/tree/master/src/resharper-angularjs/JavaScript and support for a solution specific xml with "own" directives. |
@DerAlbertCom, are you ok if I cherry pick some of those commits? I want to get back onto this, but the project's changed a lot since the branch started, so I think it might be easier to pull in the most relevant commits and work from there. How does that sound? |
Pick it. |
Those are effectively two features, so I'm happy to split it into two requests:
One is to be able to write
ng-controller="FooController"
orng-controller="FooController as vm"
and have an option toalt + Enter
to create a new controller with this name.Second one would be to navigate to definition when the controller exists.
The text was updated successfully, but these errors were encountered: