feat: add support for prettierIgnore
#266
Closed
Conversation
This file contains 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
|
As a maintainer of both this repo and Prettier, I have to say that Prettier PR is far from ready. |
Probably not the best place to have this conversation, but: what is it lacking, then? |
|
I'll review in Prettier now. |
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.
The goal of this PR is to add support for
prettierIgnore- an alternative to defining ignored paths in Prettier in a separate.prettierignorefile, consisting of an array of file blobs that should not be sorted. The key behaves exactly the same aseslintIgnoredoes (with the exception of, well... handling ignores for Prettier instead of for ESLint).The PR in Prettier hasn't been merged yet, though I imagine it will be in the nearest future.
See: prettier/prettier#12672