Change default syntax behaviour to always use safe-parser with fix regardless of extension#7357
Merged
ybiquitous merged 2 commits intomainfrom Nov 27, 2023
Merged
Change default syntax behaviour to always use safe-parser with fix regardless of extension#7357ybiquitous merged 2 commits intomainfrom
fix regardless of extension#7357ybiquitous merged 2 commits intomainfrom
Conversation
Loading
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.
Closes #7116
We no longer maintain the special file extension list for the
customSyntaxwarning and thefixoption. This means thatpostcss-safe-parseris always applied when autofix.