Remove Frozen Rules

[MarkSky]

What is the problem you're trying to solve?

From the Stylistic issues website, some rules won't be handled in the future. Could remove these rules from stylelint-config-standard?

What solution would you like to see?

When using stylelint-config-standard, there're no errors about the frozen rules.

[jeddy3]

Could remove these rules from stylelint-config-standard?

Yes, eventually. Probably alongside a major release Stylelint where we can better communicate that we're now focused on maintaining rules that help people avoid errors and enforce (non-sylistic) consistency. At the moment we're testing the waters of this change in focus, and we suggest in our getting started guide extending an appropriate shared config, e.g. stylelint-config-prettier so that this config can be used, without conflict, with pretty printers like Prettier. We'll then remove the stylistic rules from Stylelint itself and from this config later down the line.

[carlosjeurissen]

@jeddy3 If this change is pushed thru. It would be very welcome if we can make a smooth transition to one new stylelint-plugin-stylistic (or something) plugin which contains all the stylistic rules which will be removed as to have a viable alternative to the removed rules which would be fully customizable (unlike prettier).

[jeddy3]

@carlosjeurissen I agree that it'd be great if a plugin was available before the stylistic rules were deprecated in Stylelint and removed from this config.

You (or anyone else using these rules) can create the plugin now if you like. People have recently reported a few bugs with these rules (https://github.com/stylelint/stylelint/issues/6092, https://github.com/stylelint/stylelint/issues/5984, https://github.com/stylelint/stylelint/issues/5673 and so on), and having the plugin available will give them a place to fix these issues.

Once the plugin is available, we can:

• direct people to the plugin who report further issues in our issue tracker about the rules
• update our documentation to point people to the plugin so that the migration can begin gradually

Like all community things (plugins, formatters, custom syntaxes etc), the plugin should outside of the Stylelint organisation, and is best maintained by people who use it.

[Mouvedia]

I am probably in the minority but I gotta say that having to review 64 rules at once to know which ones I wanna keep is annoying. The result, for me, is that I am probably not gonna rely on stylelint-config-standard anymore for my personal config because the maintenance burden of version upgrades is becoming so time consuming that it outweighs the PROs of extending it.