Strange behavior with v-for directive
See original GitHub issueVersions:
- VueJs: 2.1.10
- Vee-Validate: 2.0.0-beta.21
Description:
I found 2 strange things:
- If we have such Vue data:
{ element: 'el', elements: ['el1', 'el2', 'el3'] }
and use vee-validate both onelement
andelement in elements
- vee-validate will validate only first. - With
v-for
directive and passingarg
property it seems not validate at all
Steps To Reproduce:
I prepared jsfiddle. Delete all in first input - you’ll see errors for this input and for 3 other inputs below. Then delete all in 3 lowermost inputs - you’ll see no errors. Hope it describes the problem well.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Possible bug, Strange behavior when using `v-if` directives ...
The strange behavior is that while playing the embedded video iframe is forced to reload when the video size is changed, but only...
Read more >javascript - Strange Behavior Of Embedded Video & v-if - Stack ...
The strange behavior is that while playing the embedded video iframe is forced to reload when the video size is changed, but only...
Read more >Understanding the v-for Update Strategy in Vue.js
Get a deeper understanding of how the v-for directive in Vue.js updates ... if you see some strange behavior when using the v-for...
Read more >Varying behavior depending on how the slot is named. · Issue ...
It does make sense to me that the value that follows the colon in the directive declaration becomes the $slots object key, and...
Read more >Why you should use the key directive in Vue.js with v-for
Although it is pretty straightforward, there can be some cases where you will end up scratching your head while everything seems to look...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve done some manual testing and it seems to be resolved, I will test few more things and will tag the new release.
I’m working on the docs atm, trying to separate the actual docs from the UI to make it easier for people to translate it, and for me to update it. I will defiantly add this to the docs to clarify it, thanks!
I will investigate the second issue tho