-
-
Notifications
You must be signed in to change notification settings - Fork 681
Nested v-for breaks variable usage detection #164
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
Labels
Comments
|
armano2
added a commit
to armano2/eslint-plugin-vue
that referenced
this issue
Aug 24, 2017
HerringtonDarkholme
added a commit
to HerringtonDarkholme/eslint-plugin-vue
that referenced
this issue
Aug 25, 2017
Fix vuejs#164, don't report error when nested v-for refers iterator. Do report error when nested v-for doesn't refer iterator.
mysticatea
pushed a commit
that referenced
this issue
Sep 1, 2017
* polish template v-for error report Fix #164, don't report error when nested v-for refers iterator. Do report error when nested v-for doesn't refer iterator. * update jsdoc * check iterator usage in new way * add more test cases * fix code style * cosmetic indentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code:
What did you expect to happen?
No error, since inner iterator
snapItem
depends onitem
, thussnapItem.id
uses both inner and outer variables.What actually happened? Please include the actual, raw output from ESLint.
Error.
The text was updated successfully, but these errors were encountered: