-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Rename "at-rules-without-declaration-blocks" to "blockless-at-rules" in max-nesting-depth #2275
Conversation
…in max-nesting-depth (#2231)
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.
Besides one very tiny docs request, this looks great to me :)
### `ignore: ["at-rules-without-declaration-blocks"]` | ||
### `ignore: ["blockless-at-rules"]` | ||
|
||
***Note: This option was previously called `at-rules-without-declaration-blocks`. See [the release planning docs](http://stylelint.io/user-guide/release-planning/) for details.*** |
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.
Let's drop the "See the release planning docs for details." bit.
I made a mistake advocating that in another PR. The releasing planning doc is a call for community help, and no help is required with these option renames.
Thanks! @jeddy3 @hudochenkov How are we handling changelog entries for the deprecations branch? |
@davidtheclark @jeddy3 I can't find any changelog messages for deprecated rules and options. Nevertheless there is an issue with a list of deprecated rules #2123 and PR with some of these rules deprecated #2197. List of deprecated options #1663 (comment) (subject to change), PR with deprecation #2213. And current PR #2275. Shall we add everything deprecated to changelog in |
Yes please! They've historically been written as:
FYI, I forgot to mention that the changelog is written in the following order:
And within each group it is order by general items first (i.e. the engine, CLI etc), follow by rule specific items (order alphabetically by the rule name e.g. "Fixed: |
@jeddy3 I'm not sure where to put these changelog records, because changelog in
|
Probably rebase Your items LGTM. I've made a couple of tweaks (edit my post to access the raw markdown):
|
Thanks @hudochenkov! |
Done. But I forgot about “Deprecations” header 🤷♂️ |
I think leaving that as Could also change it to |
Closes #2231.
No, it's self explanatory.