Text Field component not behaving correctly with validation (VeeValidate)
See original GitHub issueSteps to reproduce
- Create a
v-text-field
component - Apply validation through VeeValidate
Versions
0.14.7
What is expected ?
The component should turn red only if there are errors.
What is actually happening ?
The component is red from the very beginning and there is also an error in the console:
“[Vue warn]: <transition-group> children must be keyed: <div>”
Reproduction Link
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Field - VeeValidate
The Field component renders an HTML input tag if not specified otherwise. Which can be done in two ways. Rendering simple fields with...
Read more >Validation Provider - VeeValidate
The fields being validated must have a v-model so the component can correctly identify the element/component being validated unless the field accepts a...
Read more >Validating Dynamically Displayed Inputs - VeeValidate
A common case is to use v-if to display a field or two based on some sort of criteria, for example you could...
Read more >Cross Field Validation - VeeValidate
Properly reference the target field name or vid value in the rules of the other. This can be confusing at first, you can...
Read more >Basics - VeeValidate
If you are not using a bundler and using vee-validate in the browser or from a ... For the input field or the...
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
This is currently being worked on. We are refactoring the internal validation and how we support 3rd party libraries.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord