Deprecate --no-autoprefixer flag in the CLI
#11280
Merged
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
0a09a6c to
ada1a25
Compare
dbebe65 to
650852d
Compare
ada1a25 to
947c6fc
Compare
b4a8d65 to
ac3c1cd
Compare
--no-autoprefixer in the CLI--no-autoprefixer in the CLI
712a333 to
5e537f4
Compare
--no-autoprefixer in the CLI--no-autoprefixer flag in the CLI
5e537f4 to
c290b86
Compare
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.
This PR handles the
--no-autoprefixeroption in the CLI now that we are using Lighting CSS.It works by setting the
targetstoundefinedwhich takes care of it all.This PR also includes a test with
--no-autoprefixerin combination with nesting such that we can guarantee that nesting still works as expected even if we ignore the targets.