FieldBag not working as expected
See original GitHub issueHello,
when I try to access the flags of a field using the method accessors, they don’t update when their underlying value changes. However, the errorBag does update. Is this behaviour expected, or am I missing something?
computed: {
testField() {
// will only be evaluated once and won't update again, always returns initial value
return this.fields.passed('channel')
},
testError() {
// returns the error or null as expected when the value changes
return this.errors.first('channel')
}
}
Regards, Andreas
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Customer reviews: Canvas Field Bag - Olive DT702
I really love that pocket. The only problem I ever encountered was that snapping the cover shut when the bag was empty, wouldn't...
Read more >Filson Medium Field Bag Review
... the actual useable size is a little tricky because the opening at the top of the bag is not the full 15”...
Read more >Fluor Field Bag Policy | Drive - Minor League Baseball
The Drive encourage fans not to bring any bags, however, the following will be permitted: Clear bags and backpacks are permitted; Medical Bags...
Read more >Citi Field Bag Policy | New York Mets - MLB.com
All purses, diaper bags that are not backpack-style, tote, drawstring and ... At this time, no other changes are being made to our...
Read more >Medium Rugged Twill Field Bag - Filson
heart-shaped wishlist icon. Save for Later. Add · truck shipping icon. Expected to ship in 48hrs. Shipping · rubber stamp guarantee icon. Filson ......
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
Being able to use
errors
in computed properties or to pass them to a component would be useful. This way you could create anErrorComponent
where the errors would be styled and displayed appropriately.For example:
<form-error :errorBag="errors" element="user.dog_name" scope="form-3"></form-error>
Seems like the validation result is shifted for some reason, I will look into it.