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
I'm trying to migrate plain reducer component that handles updates/validation of my form to re-formality. My form is complex and I'm having a hard time thinking about correct values/fields/updaters. Here is a type of the state:
For me, it's a really hard example. I want to have all functionality (like validation) available for even most nested values. Current API allows you to manage "one level deep" state really good but more complex state would require a lot of duplicated logic to update nested fields, a lot of fields, values etc.
Do you have any ideas on how we can improve re-formality API to better handle cases like this or how to approach this in application code using current API?
The text was updated successfully, but these errors were encountered:
This is somewhat similar to #29 and I haven't looked into complex examples yet. Can't promise anything concrete but I'll look into forms w/ complex structure sooner or later.
I'm trying to migrate plain reducer component that handles updates/validation of my form to
re-formality
. My form is complex and I'm having a hard time thinking about correct values/fields/updaters. Here is a type of the state:For me, it's a really hard example. I want to have all functionality (like validation) available for even most nested values. Current API allows you to manage "one level deep" state really good but more complex state would require a lot of duplicated logic to update nested fields, a lot of fields, values etc.
Do you have any ideas on how we can improve
re-formality
API to better handle cases like this or how to approach this in application code using current API?The text was updated successfully, but these errors were encountered: