plugins-stylelint/no-at-nest-rule
#997
Merged
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
…c-zebra-shark-a8b34dabd3
…at-nest-rule--empathetic-zebra-shark-a8b34dabd3
…at-nest-rule--empathetic-zebra-shark-a8b34dabd3
| @@ -147,6 +147,11 @@ export const osiApprovedWithCCO = [ | |||
| ]; | |||
|
|
|||
| const licenseExceptions = [ | |||
| { | |||
| // because ... irony? 🤷 | |||
Antonio-Laguna
approved these changes
Jun 13, 2023
There was a problem hiding this comment.
@romainmenke I agree completely!
I like how nice the tests are.
Does this need any special handling from the release script?
I ran the dry run thingy and that indicated that it would just work. |
romainmenke
deleted the
plugins-stylelint/no-at-nest-rule--empathetic-zebra-shark-a8b34dabd3
branch
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.
A Stylelint plugin to change nested css with
@nestto css without.Effectively migrating to the latest specification.
I am not going to bother supporting the non-standard nesting that Chrome and Safari shipped.
i.e. I am not going to wrap stuff with
:is().The most important thing for us is that our users stop using
@nest.@Antonio-Laguna We discussed at some point that we would also create a monorepo for the Stylelint plugins under
@csstools. I think this is still worthwhile but separate from this change.If any Stylelint plugins are created in this repo they should be tightly coupled to a PostCSS plugin.
Let me know if you disagree :)