Prop name collision
See original GitHub issueVersions:
- VueJs: 2.0
- Vee-Validate: 2.0.0-beta.17
Description:
Using plaging vutable-2 and got this error
Uncaught TypeError: this.fields.forEach is not a function
It’s no doubt name collision, can you plz add prop fields
, like you did with error
?
Steps To Reproduce:
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
React prop name collision between 3rd-party libraries
How can I can prevent errors between 3rd-party libraries when they use the same prop name but expect different data types for that...
Read more >Name Collision Resources & Information - ICANN
A name collision occurs when an attempt to resolve a name used in a private name space (e.g. under a non-delegated Top-Level Domain, ......
Read more >React prop name collision between 3rd-party libraries-Reactjs
Coding example for the question React prop name collision between 3rd-party libraries-Reactjs.
Read more >Deprecation: Resource Property Name Collision (CHEF-11)
Modify the resource and choose a different name for the property that does not conflict with an already-existing method name. © Copyright: This...
Read more >Prop name collision between 3rd-party library and MUI #11680
Prop name collision between 3rd-party library and MUI #11680 ... for form validation, which sends an error message as a prop named 'error':...
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
@logaretm thx, now it works 😃 👍
Ah I think I understand, you can rename the fields name when installing the plugin:
Its not documented because it will cause issues for Vue 1.0 version, I will document it once resolved.