question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prop name collision

See original GitHub issue

Versions:

  • 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:closed
  • Created 7 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
SergeyMiraclecommented, Dec 3, 2016

@logaretm thx, now it works 😃 👍

1reaction
logaretmcommented, Dec 3, 2016

Ah I think I understand, you can rename the fields name when installing the plugin:

Vue.use(VeeValidate, {
    fieldsBagName: 'whatever'
});

Its not documented because it will cause issues for Vue 1.0 version, I will document it once resolved.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found