Scott Newcomer
Scott Newcomer
@sandstrom That is an interesting idea. I like it. I'll see if I can put up a psuedo RFC at some point in the next few weeks.
@basz Happen to have more information?
@basz Mind trying out the latest 3.5.7 if you don't mind and let me know if this is still an issue?
I'm not sure I see an issue in this specific repo. Glimmer components use `this.args` && `@value`. Old reactivity paradigms like `didReceiveAttrs` and `computed` (push based system) **may** be at...
My first inclination would be to ensure BsForm is migrated completed to new glimmer semantics. That means removing things like `didReceiveAttrs` (arguments to glimmer components are now autotracked) and `computed`....
That looks like a better example! Thank you. I think #492 captures how we need to refine our autotracking abilities. Specifically `tracked-built-ins`. Basically b/c we reset `this[CHANGES]` the whole tree...
Reopen to see if we can use `tracked-built-ins`
I'm all for merging #586. `notifyPropertyChange` on a nested path is in fact wrong and shouldn't work as it is per-object observability. The PR fixes KVO observability! Just a few...
👋 @lindyhopchris Do you happen to have a reproduction? I added a test [here](https://github.com/validated-changeset/validated-changeset/pull/92) and all seems ok. We only rollback changes made through the `changeset`. Does `DS.errors` get set...
Oh you are right. I naively assumed the errors from the API would be set and persist regardless of the DS.Model value. So it must clear out the errors when...