useFluentForm returns multiple objects containing data for each field:
These field data are grouped by their concerns (e.g. the concern of
values is to store all current values).
This can be perfectly fine for a lot of apps, but for others it could limit the possiblities to design the architecture.
It might be more useful to put all information, that belongs to a field, into one place. Instead of having
fields etc. you could've e.g.
password objects that contain properties for
useFieldData receives a fluent form instance as parameter and will put all information for each field in a seperate object:
Following example contains a fluent form with two fields:
useFieldData will reorganize the state returned by
useFluentForm and group field data by the field itself: