fix(@angular/cli): ignore unknown files when formatting schematic changes#32595
Merged
alan-agius4 merged 1 commit intoangular:mainfrom Feb 26, 2026
Merged
Conversation
…nges When schematics modify files such as .gitignore, Prettier cannot infer a parser and formatting fails. ``` npx prettier --check .gitignore [error] No parser could be inferred for file ".gitignore". ``` With ignore-unknown enabled, Prettier does not throw this parser error
alan-agius4
approved these changes
Feb 26, 2026
Collaborator
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
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.
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 schematics modify files such as .gitignore, Prettier cannot infer a parser and formatting fails.
What is the new behavior?
With
ignore-unknownenabled, Prettier does not throw this parser errorDoes this PR introduce a breaking change?
Other information