You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is cumbersome to declare for each config because Vue SFCs are always in .vue files.
Your take on the correct solution to problem.
When an extension/pattern is set via overrides, the extension no longer needs to be manually passed into ESLint via the --ext flag.
I would like to recommend that configs use overrides so ESLint can automatically detect .vue files without the user needing to pass it in:
{"overrides": [{"files": "*.vue",// ...}]}
Other info
Applying the plugin rules specifically to .vue extensions should make it easier to handle conflicts like this:
This rule only checks `.vue` files and does not interfere with other `.js` files. Unfortunately the default `indent` rule when turned on will try to lint both, so in order to make them complementary you can use `overrides` setting and disable `indent` rule on `.vue` files:
The text was updated successfully, but these errors were encountered:
Thank you for posting the issue,
I think maybe we can move only the parser config to *.vue since the rules may also check *.js files.
Since it's a breaking change, it should be done in a major version, but I don't know yet if it will be in the next major version.
Since the ESLint team is planning a new flat config, we may provide a completely different shareable config. https://eslint.org/blog/2022/08/new-config-system-part-1/
The problem you want to solve.
Currently, the docs recommend passing the
.vue
extension in via CLI: https://eslint.vuejs.org/user-guide/#usageThis is cumbersome to declare for each config because Vue SFCs are always in
.vue
files.Your take on the correct solution to problem.
When an extension/pattern is set via
overrides
, the extension no longer needs to be manually passed into ESLint via the--ext
flag.I would like to recommend that configs use
overrides
so ESLint can automatically detect.vue
files without the user needing to pass it in:Other info
.vue
extensions should make it easier to handle conflicts like this:eslint-plugin-vue/docs/rules/script-indent.md
Line 67 in 9673a61
The text was updated successfully, but these errors were encountered: