Have test specs files use .name property instead of hardcoded string#2
Open
scotch83 wants to merge 2 commits intoangular:mainfrom
Open
Have test specs files use .name property instead of hardcoded string#2scotch83 wants to merge 2 commits intoangular:mainfrom
scotch83 wants to merge 2 commits intoangular:mainfrom
Conversation
feat: allow rename of describe test
Update __name@dasherize__.__type@dasherize__.spec.ts.template
Author
|
If you guys find this useful, I can provide a merge request for all others, or integrate on this one. |
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
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.
When using the angular schematic for generating components, this is always using a hardcoded string instead of a .name property for the class name, which will enormously help with the renaming tools.