Replies: 1 comment 1 reply
-
I am experiencing the same issue as this, are there any updates? In my case, I am calling It appears perhaps there is a bug in some This issue is very easily reproduced so I can provide a code sandbox example that is helpful. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In a child component I'm watching a value, and setting another value when it becomes true:
Basically prefilling
alternateAddress
withcompanyAddress
. So far this is working perfectly fine.Higher up in a parent component where the form is maintained, there's a watch going on that needs to trigger in order for an onChange event to get fired:
The trouble is, for some reason, this watch only doesn't fire when the above
setValue
is called. I can place a console.log in there and it will happily work for when thatuseAlternateAddress
gets changed, but it won't work for whenalternateAddress
gets changes as a result ofsetValue
.setValue
reflected in the UI, so it's doing a rerender and everything.alternateAddress
in the UI, just like any other field.I didn't see anything significant in the rules section about pre-existing watches. So I guess that's the question then: what are the rules?
Beta Was this translation helpful? Give feedback.
All reactions