fix(@schematics/angular): format template files to match Prettier conf #30916
+71
−51
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
…figuration Applies consistent formatting to Angular schematic template files to prevent changes when Prettier is executed on freshly generated files. The templates now respect the formatting configuration defined in package.json.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Applies consistent formatting to Angular schematic template files to prevent changes when Prettier is executed on freshly generated files. The templates now respect the formatting configuration defined in package.json.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When we format a file using Prettier on a freshly generated project, it reads the configuration in the package.json and formats the file. It would be nice if the templates were already formatted correctly to avoid unnecessary git changes.
Issue Number: N/A
Templates are formatted following the configuration set in package.json
Does this PR introduce a breaking change?
Other information