Open ntnyq opened 1 year ago
Thank you for this issue.
It seems to be missing documentation. new Vue()
has been the target of linting since eslint-plugin-vue v3.
If you want to exclude new Vue()
, we'll need to add an option to each rule or fix it.
Thank you for this issue. It seems to be missing documentation.
new Vue()
has been the target of linting since eslint-plugin-vue v3.If you want to exclude
new Vue()
, we'll need to add an option to each rule or fix it.
Can this option be added tovue-eslint-parser
's parserOptions.vueFeatures
so it can be easy configured?
Can this option be added tovue-eslint-parser's parserOptions.vueFeatures so it can be easy configured?
Can not do that. parserOptions.vueFeatures
has nothing to do with linting target detection.
Checklist
Tell us about your environment
Please show your full configuration:
What did you do?
What did you expect to happen?
Everything works fine and no error reported since
new Vue
is not listed in docs - eslint-detect-components.What actually happened?
ESLint reported 2 errors:
Repository to reproduce this issue
https://github.com/ntnyq-dev/repro-eslint-plugin-vue
Related rules
vue/require-name-property
vue/padding-lines-in-component-definition
Additional
If it is expected, how can I exclude it from being checked?