-
Notifications
You must be signed in to change notification settings - Fork 62
[FEAT] [BREAKING] [no-unused-vars] remove implicit dep on base rule #260
Conversation
I’m wondering if we should be copying ESLint’s docs or just linking to them. I’m in favor of linking to the original docs and describing how our rule is different. This allows us to have the most up-to-date docs for the rule that we’re building on, and makes it easier for folks to see how our rule differs. |
It's not really good idea to do it for no unused vars, other plugins can modify eslint used property, and there can be side effects when using this with eslint-plugin-vue |
We shouldn't enable eslint rules anyway.. |
@armano2 - this won't break eslint-plugin-vue. {
"no-unused-vars": "off",
"typescript/no-unused-vars": ["error", { config }],
"vue/no-unused-vars": "error"
} I think in this case it's fine because we are a language-level plugin. @j-f1 I actually thought the same thing. I copied it because that's what we'd done for the other rules. |
fair enough i didn't think about
|
Fixes #144 Requires ~~#259~~, ~~#260~~. - added a util to make it standardised and easier to add default config for a rule - configured recommended based on #144 - purposely switched `recommended` prop to be `"error" | "warning" | false` - inside the eslint repo, it should be `true`. otherwise it's just a property that isn't used officially by eslint. It's truthy so `eslint-docs` still work. - changed recommended generator to accept `"error"`/`"warning"` for more configurability. - adjusted default config of certain rules that didn't match our recommendations.
Similar to what we've done with both indent, and camelcase.
Rather than forcing users to configure both our rule and the base rule (which has been a source of confusion), this lets users just use our rule.