-
-
Notifications
You must be signed in to change notification settings - Fork 75
nesting editions #1305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nesting editions #1305
Conversation
…igent-alaskan-malamute-d9a22039d1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome idea and great execution! Love this path forward!
); | ||
|
||
if (options.noIsPseudoSelector) { | ||
throw new Error('The `noIsPseudoSelector` option is no longer supported. Migrate your CSS to use the latest CSS nesting syntax.'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't throw here because postcss-preset-env
sets this option when a user targets very old browsers.
That behavior already has a comment to remove it in a next major.
Thank you reviewing @Antonio-Laguna 🚀 |
This adds a plugin option
edition
to toggle between implementations.The
edition
doesn't refer to a specification version, but rather our implementation.Edition
2024-02
overview::is()
pseudo-class is no longer optionaland
keyword@nest
is removed from the specificationI am choosing not to re-order declarations and nested rules in this new edition because we actually know that this is a major pain point and I want to give users hands on experience with what it could be if w3c/csswg-drafts#8738 is adopted.