[Bug] Error reactivity with validateAll (and validate?)
See original GitHub issueI upgraded from 2.1.0-beta.2 to 2.1.0-beta.4.
My setup before was: I have inject: false on my config, and each of my page-level forms use a Formable mixin which request a new validator instance (or a new validator scope now). I have a generic Form component which has some standard saving functionality used across the site. So, all of my page-level forms use the Form component. The Form components injects the validator scope from the page-level parent.
Since the update, upon running validateAll on the form, errors no longer appear under the inputs (when they’re using errors.first(field, scope)), even though the error bag has errors.
I tested and it seems like this.errors may be having some reactivity problems, as setting a watcher on errors fired for changes in beta.2 but not beta.4. Don’t know if that’s actually the problem or if my setup is invalid for the newest version.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (8 by maintainers)

Top Related StackOverflow Question
OK, I reverted a change that might have broken the reactivity, tagged a beta.5 release since I’m going off for the next week.
Updated the title for visibility in case anybody else ran into this