-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
vue/no-unused-property
false positive with camelCase v-bind
same-name shorthand
#2370
Comments
|
vue/no-unused-property
false positive with camelCase v-bind
same-name shorthand
This issue has been fixed by vue-eslint-parser. See: https://ota-meshi.github.io/eslint-plugin-vue-demo/#eJxVjDEKwzAMRa8iNCcEOhqTsRfomiWNlWJwLSPLoWB892KSod0+7/NexY0doUGr9E5hVZqXCGCdP8A8V7kzw/SPxv1idvpxbN7EJ53pk1gUHO1rCQq1q0k4ZXNugLNq4KHi42vosC2x9d7VWCIOKCVQRlPxKDRFHkssmdzYWyTq+3dr7Qt/ZUJc Maybe we can close this as completed. |
Glad to see that! However I haven't |
This issue can only be closed when the Meanwhile, you can manually run |
Here it is #2379 @FloEdelmann 😉 |
Thanks! Can't wait for the next release 😄 |
Checklist
Tell us about your environment
Please show your full configuration:
What did you do?
What did you expect to happen?
No EsLint warning about "unused"
tuut
propWhat actually happened?
warning 'tuut' of property found, but never used vue/no-unused-properties
Repository to reproduce this issue
https://github.com/vuejs/eslint-plugin-vue
Don't be evil, it's not always needed 🙄
The text was updated successfully, but these errors were encountered: