-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
499 Invalid prop definition crash #506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It looks like vee-validate is doing quite weird things with props. I added a guard against invalid prop definitions. This is so edgy I don't know if it's really the devtools that should have fix for this or vee-validate. Thoughts @yyx990803? |
@logaretm ⬆️ |
Also, the issue doesn't seem related to provide/inject. |
I can provide a fix on my end. But what is considered an invalid prop? vee-validate adds mostly adds data/computed fields to the components in the And there is the |
@Akryum My guess is correct. The this.$options.computed[options.fieldsBagName || 'fields'] = function fieldBagGetter () {
if (!Object.keys(this.$validator.flags).length) {
return fakeFlags;
}
return this.$validator.flags;
}; The check Removing the check fixes the issue in my local tests. I can push a release quickly and I would appreciate it if you can point out other violations that are being done by vee-validate so I can address them too. EDIT: Wording |
From what I understand, |
Also, the name resolved for it is something like |
But it isn't a component nor a prop, is it? so to clarify It just looks like one and gets interpreted as one and this caused the issue. |
We check if |
Fix #499