-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
docs: typo #534
docs: typo #534
Conversation
docs/guide/migration.md
Outdated
// your own rules | ||
{ | ||
plugins: { | ||
stylistic: StylisticPlugin | ||
}, | ||
rules: { | ||
'stylistic/semi': 'error', | ||
'@stylistic/semi': 'error', |
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.
No, this is not how it works. The previous example is correct as we provide the plugin named as stylistic
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.
my bad, removed
I was confused with all the other examples that name the plugins with @
prefix (e.g. @stylistic/js
)
don't you think we should rename it to @stylistic
here?
{
plugins: {
'@stylistic': StylisticPlugin
},
rules: {
'@stylistic/semi': 'error',
// ...
}
}
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.
@stylistic
was mainly the convention of the legacy config, where in the flat config I don't want users to carry that legacy convention when they don't need to.
Fix comments
Description
Unnecessary comma cause diff addition not to show + missing @ before
stylistic
: