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
Deprecate stylistic rules handled by Prettier #6504
Changes from 2 commits
81a02b7
6f516b5
e1fe14a
2be55ee
bdcf94e
d9ff205
0732ce9
0b37311
9f04234
09e5a50
23a4e75
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -23,6 +23,7 @@ const messages = ruleMessages(ruleName, { | |||||||||||||
const meta = { | ||||||||||||||
url: 'https://stylelint.io/user-guide/rules/block-closing-brace-newline-after', | ||||||||||||||
fixable: true, | ||||||||||||||
deprecated: true, | ||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I wanted to check whether all the rules that were being deprecated were properly covered by prettier. This one has options:
Are all of these properly covered by prettier?
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @Mouvedia was please suggested list created? To see which deprecated rule can be covered by the prettier replacement? Thanks. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ideally, we might make a list, but we need more resources. Also, it may not be precious since the rules will be removed in the next major update. However, we welcome your contribution if you have time. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Following on from #6657 (comment), I suggest the people working on the plugin pack draw up the list. As @ybiquitous said, we've other things to focus on (that will benefit most of our users). I suspect most people already use a pretty printer alongside Stylelint (as we've been advocating that approach for over a year now in our docs), and most of those who don't will soon, as it's our recommended approach in our new migration guide. Anyone wanting to continue using Stylelint for formatting can work together on a community plugin pack. As with custom syntaxes, the health of the plugin will be determined by the health of the community that maintains it. |
||||||||||||||
}; | ||||||||||||||
|
||||||||||||||
/** @type {import('stylelint').Rule} */ | ||||||||||||||
|
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.
[ask] I believe the warning message is helpful, but what do you think?
[note] GitHub renders the
> **Warning**
text as follows:On the other hand, Docusaurus has a different rendering syntax called Admonitions. E.g.
If using Admonitions, we need to rewrite the warning syntax on the stylelint.io repo.
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.
LGTM
Yes, but only if it's quick to do as:
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.
Agree. It looks like we don't need to add an extra process.