Warning [vee-validate] rules must be either a string or an object
See original GitHub issueVersions:
- VueJs: 2.5.16
- Vee-Validate: 2.1.0-beta.5
Description:
I’m getting the following warning every time I refresh my page.
Warning [vee-validate] rules must be either a string or an object
It started when I updated my VeeValidate to the beta one. In the 2.0.9 it won’t show the warning.
I’ve already checked the entire code looking for some miss use off v-validate but it’s all correct (I’m using object form).
Can someone help me?
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Custom Rules - VeeValidate
This validator object must have a validate method and can contain a getMessage method which will be merged into the current dictionary locale....
Read more >Rules Object Expression - VeeValidate
This rules object expression like the name suggests, uses JavaScript/JSON objects to define validation rules and generally is much more powerful than string...
Read more >Error Messages - VeeValidate
They can be either strings or functions that return a string called generators. ... WARNING. You must provide the messages in an object...
Read more >Available Rules - VeeValidate
The field under validation must have exactly have the specified number of items, only works for iterables. Allowed Iterable values are: string ,...
Read more >Validation Provider - VeeValidate
The fields being validated must have a v-model so the component can correctly ... failedRules, [x: string]: string, A map object of failed...
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 Free
Top 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

Thanks for the small demo, it was resolved and should be up in the next release.
I get the same thing. Here’s my config: