stylelint: Deprecate declaration-block-properties-order

Ref: https://github.com/stylelint/stylelint/issues/2010

  • Add deprecation warning.
  • Add tests for deprecation warning.
  • Update changelog (post merged) - “Deprecated: declaration-block-properties-order rule. Use the community stylelint-order plugin pack instead. See the release planning document for more details.”

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 30 (28 by maintainers)

Most upvoted comments

remind me (once again) that any repo that is in or moved to the stylelint organisation will have regardless of how the repo is configured will have an implied status that it is maintained by the stylelint organisation.

The point is that plugins are good for users, good for maintainers, good for the community, and we shouldn’t be afraid of them. Plugins can and should provide functionality that some users consider essential.

I think these two bits come together nicely to summarise the final points.

well, let’s leave it at that then

Good stuff. Thanks for discussion everyone. Lets be sure to keep the key points of this discussion in mind should the issue pop up again.

We’ve found that rules to enforce property order, property groupings, etc., work better as plugins, because there are so many different opinions about what to enforce, and how. When you write or use a plugin, you can make sure to enforce your own particular preferences, exactly; but a rule that tries to address too many divergent use-cases becomes a mess. Plugins are easy to incorporate into your configuration.

This is really nice. I suggest we add it to this entry of the FAQ. Perhaps fleshing out that FAQ entry a little too. I’ll create a separate issue for it.

So, back to the issue at hand… I’ll probably have time this week to add the code to deprecate declaration-block-properties-order if no one beats me to it.

@jeddy3 what about move stylelint-order to stylelint org? My opinion was that, the basics rules should be either in the core or in the organization. In life happen different good and bad things and contributor(s) may not have the ability or time to fix something or add or change. This will cause the inability to handle requests from the community associated with sorting features, declaration, etc., which will be negative effects for us. After reviewing the configuration of other organizations, I see that these rules are almost all that once again says that the community needs these rules on the basis of this it seems to me that they belong in the core.