Platform: macOS
Vetur version: 0.8.6
VSCode version: 1.13.1
'v-model' directives aren't supported on \
My suggestion is using another name for custom component. Case sensitivity is only supported in SFC and not html compliant.
@mysticatea however, eslint-plugin-vue should be either consistently case insensitive or sensitive, not sometimes.
can doesn't imply should. The doc also explicitly states:
This means that the PascalCase is the most universal declaration convention and kebab-case is the most universal usage convention.
but I think, It's doesn't imply should not.
It's vue template, and It's virtual computing, case sensitive doesn't imply wrong, and It's supported.
Try this:
new Vue({template: '<Div>Im div, case insensitive</Div>'}).$mount()
new Vue({template: '<NoExist>Error</NoExist>'}).$mount()
Vue's string template and SFC are case insensitive for html compliance. It seems hard to correctly tell a custom component from a misspell native tag name without resolving the components field of component associated with the template.
Also, when you register a component with the same case insensitive name as native tag. Vue warns Do not use built-in or reserved HTML elements as component id: Select.
I think you are consider the wrong direction,
if you say we should case insensitive, regardless of whether my component is custom, it's just a \
Please file this issue on https://github.com/vuejs/eslint-plugin-vue .
@octref this issue is was solved some time ago in vue-eslint-parser/plugin and you should consider updating version up to 3.13.0 from currently used 3.8.0
cc: @thearabbit @HerringtonDarkholme @vvpvvp
@vvpvvp @armano2 We've already upgraded to 3.13.0
https://github.com/vuejs/vetur/blob/master/server/package.json#L21
The fix will be released in next version, soon.
Released 0.9.6.
Most helpful comment
@vvpvvp @armano2 We've already upgraded to 3.13.0
https://github.com/vuejs/vetur/blob/master/server/package.json#L21
The fix will be released in next version, soon.