You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After choosing "no," the object should be { yesOrNo: 'No', whyNot: null, anotherField: null }. Instead, the resulting object is just { yesOrNo: 'No', anotherField: null }. Even submitting the form won't cause the key to populate; it only shows up after changing "Another field."
The text was updated successfully, but these errors were encountered:
Context: When two or more Fields are used either inside the Conditional component or both
in their own Conditional with the same show condition, only the last
Field receive its initial value set in item attribute via Formol
component.
The cause: when a Field is mounted, the register function is executed to
register the component in transientItem variable. But due to the async
nature of setState, the transientItem between Fields registration stays
the same.
I think this commit is an attempt to fix the bug c12d07c
But it seems to appear again #62
Fields placed inside a
<Conditional>
only populate in the validator object after another field is modified.After choosing "no," the object should be
{ yesOrNo: 'No', whyNot: null, anotherField: null }
. Instead, the resulting object is just{ yesOrNo: 'No', anotherField: null }
. Even submitting the form won't cause the key to populate; it only shows up after changing "Another field."The text was updated successfully, but these errors were encountered: