Feature/rename all angular suffixes to v21 styleguide #341
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rename Angular Component, command: Rename all Angular suffixes to v20 styleguide
…Removal Script README.md Fix for namespace collisions with purpose aware renaming for uniqueness
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello all
I'm hoping you'll find this useful.
I've applied the Angular v20+ Styleguide Naming Convention to your project, using a VS Code extension, Rename Angular Component with the command "Rename all Angular suffixes to v20 styleguide". I then repaired all namespace collisions using an AI prompt that derives the class's purpose and renames it to make the class name unique.
I really hope you like it. Or at least, quite like it.
Tom