-
-
Notifications
You must be signed in to change notification settings - Fork 591
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
'v-model' directives aren't supported on <Select> elements. #303
Comments
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:
|
but I think, It's doesn't imply should not. |
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 Also, when you register a component with the same case insensitive name as native tag. Vue warns |
I think you are consider the wrong direction, |
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 |
@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. |
Info
Platform: macOS
Vetur version: 0.8.6
VSCode version: 1.13.1
Problem
'v-model' directives aren't supported on <Select> elements.
<Select> is a custom component.
The text was updated successfully, but these errors were encountered: