Deprecation of root rules
See original GitHub issueSee the thread here - https://github.com/stylelint/stylelint/issues/2226
It seems likely that if we want to keep these rules we should come up with a stylelint plugin. Maybe a good time to discuss the validity of the three root rules:
custom-property-no-outside-root
root-no-standard-properties
selector-root-no-composition
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Deprecation Policy - Doctrine: PHP Open Source Project
Using @deprecated and PHPStan Deprecation Rules ... The primary and preferred method for deprecating functionality within Doctrine is by using the @deprecated ......
Read more >eslint-plugin-react/no-deprecated.md at master - GitHub
Several methods are deprecated between React versions. This rule will warn you if you try to use a deprecated method. Use the shared...
Read more >.htaccess Deprecation and Alternatives - Support Center
WP Engine will be deprecating the .htaccess file in order to increase website performance and match industry trends.
Read more >List of AWS Config Managed Rules
You can use the following AWS Config managed rules to evaluate whether your AWS resources comply with common best practices.
Read more >The Law of Root: A Woodland Game of Might and Right
If two game effects occur simultaneously, the player taking the current turn chooses their order, unless otherwise noted.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Done in https://github.com/suitcss/stylelint-suitcss
Will open a PR on the Stylelint repo
I think you might want to write them as single plugins (focused code that is easy to test), but publish them as a plugin pack (like stylelint-scss or stylelint-order). Publishing as a plugin pack is just as easy as publishing single plugins.
You can use a common namespace, e.g.
suitcss/
for each of the plugins.For an example of converting a core rule to a plugin, you can take a looksie as stylelint-no-browser-hacks — which is a convert of core no-browser-hacks rule.
Also, feel free to mention me if you’ve any questions 😃