feat(@angular/cli): automatic formatting files modified by schematics #32367
+93
−4
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
alan-agius4
added
action: review
angular-robot
bot
added
detected: feature
alan-agius4
force-pushed
the
formatter
branch
from
3cc3fdf to
1b984f1
Compare
clydin
approved these changes
Jan 27, 2026
Comment on lines
57
to
64
| await execFileAsync(prettierCliPath, [ | ||
| '--write', | ||
| ...[...files].filter((f) => fileTypes.has(extname(f))).map((f) => relative(cwd, f)), | ||
| ]); |
Member
There was a problem hiding this comment.
On Windows, this might need the shell option enabled.
Collaborator
Author
There was a problem hiding this comment.
I guess we'll see when this is merged.
packages/angular/cli/src/command-builder/schematics-command-module.ts
Outdated
Show resolved
Hide resolved
alan-agius4
added
action: merge
alan-agius4
force-pushed
the
formatter
branch
from
f5ca400 to
b8a64b8
Compare
This change introduces automatic formatting of files generated or modified during a schematic execution. When a schematic is executed, the CLI will now attempt to find and use the project's local Prettier installation to format all created or updated files. This ensures that generated code adheres to the project's established coding style without requiring developers to manually run a formatting command. If Prettier is not installed in the user's workspace, the formatting step will be gracefully skipped. This avoids adding a direct dependency on Prettier to the CLI and respects the user's project setup. The implementation leverages the Prettier CLI directly for a more robust and reliable formatting process. Closes angular#10777
alan-agius4
force-pushed
the
formatter
branch
3 times, most recently
from
a10a6ca to
f6721ed
Compare
alan-agius4
force-pushed
the
formatter
branch
from
f6721ed to
fde5365
Compare
Collaborator
Author
|
This PR was merged into the repository. The changes were merged into the following branches:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change introduces automatic formatting of files generated or modified during a schematic execution.
When a schematic is executed, the CLI will now attempt to find and use the project's local Prettier installation to format all created or updated files. This ensures that generated code adheres to the project's established coding style without requiring developers to manually run a formatting command.
If Prettier is not installed in the user's workspace, the formatting step will be gracefully skipped. This avoids adding a direct dependency on Prettier to the CLI and respects the user's project setup. The implementation leverages the Prettier CLI directly for a more robust and reliable formatting process.
Closes #10777