-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Allow bind syntax for "label-has-for" #529
Comments
can you provide a short reproduction of this behavior so we can try fixing it properly? |
This is yet another barrier to Vue3 adoption. If Vue allows binding with :for then this should be part of the linting rules. |
As far as I could tell, it is a problem both in vue@2 and vue@3, but anyway, could you, then, provide a reproduction link? |
There's an example - Vue SFC Link And regarding the Vue3 comment, I just started encountering this issue as I was forced to upgrade to Vue3 and used the ESLint AirBnB preset. That preset required me to get familiar with disabling a lot of rules that just didn't work with legit code like this one. |
Any updates on this topic? |
A PR would be merged if someone wants to put one together. |
So, I just gave this a look, and I'm pretty sure that this is an issue with your configuration, also it should be related to this other issue: #54 (in this other issue there are some recommendations of workarounds, but PRs are still welcomed to fix that issue). and as far as I can tell, it does not have anything to do with Vue@3. The reproduction I made is here: https://github.com/vhoyer-bug-reproductions/eslint-plugin-vuejs-accessibility if you think there was a mistake in my judgement feel free to re-open this issue EDIT: as the reproduction link provided didn't have any information about the configuration used, I assumed the recommended |
Thanks for sharing the reproduction code example. Going along your configuration over there fixed the issue for me! |
We sometimes have components that combine form elements and labels:
id
in this case is a property set on the custom component.Unfortunately the plugin ignores
:for
completely and complains about missingfor
attribute.The text was updated successfully, but these errors were encountered: