-
Notifications
You must be signed in to change notification settings - Fork 117
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
Rename files support #815
Comments
I see that the Angular CLI discussion has been closed as responsibility has shifted here. |
This would be a cool feature. I read the previous issue in the angular cli project and I agree, it is super annoying to rename the files manually. |
In the meantime, here is an alternative solution: I've created an Extension for VS Code to do all of these steps for you. It's called Rename Angular Component. I have hopes of porting it to WebStorm and a Schematic later. Previously, it took at least three semi-automated steps in VS Code as a minimum. This Extension does all of them. I realise this is promoting my own solution. But it is free, open source, and a complete answer. If it doesn't do everything you're looking for, you can post issues on the repo, and it will be improved. |
Is your feature request related to a problem? Please describe.
There are a few problems to consider:
templateUrl
andstyleUrls
references.foo.component.ts
tobar.component.ts
will still export aFooComponent
definition, which can be confusing.Describe the solution you'd like
The Angular language service could plug in to the "rename file" operation to handle all three use cases.
templateUrl
andstyleUrls
properties.*.component.ts
file could also rename the actual component symbol being exported (I'm not 100% convinced this is a good idea, but worth considering at least).Describe alternatives you've considered
Alternative is to basically do this all manually. There are some scripts and custom schematics suggested in angular/angular-cli#900, but the language service can be a lot smarter than the CLI here.
Additional context
Spin off from angular/angular-cli#900.
The text was updated successfully, but these errors were encountered: