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
What is the first use case for having the default field values attached to the useFieldArrayfields elements along with the generated field id? Is anyone aware that these values are not the current field values, but default values that don't cause a re-rendering of the field value change? Would it be critical to update the API to remove them completely?
@bluebill1049 I'd also like your thoughts on why the `fields' object is the way it is: it has the default field values attached.
I have a few ideas on how to reimagine the useFiledArray API to address some pain points.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What is the first use case for having the default field values attached to the
useFieldArray
fields
elements along with the generated fieldid
? Is anyone aware that these values are not the current field values, but default values that don't cause a re-rendering of the field value change? Would it be critical to update the API to remove them completely?@bluebill1049 I'd also like your thoughts on why the `fields' object is the way it is: it has the default field values attached.
I have a few ideas on how to reimagine the
useFiledArray
API to address some pain points.Beta Was this translation helpful? Give feedback.
All reactions