As I understand from the documentation for the reaction form, you usually place the reducer format the root of your reducer tree, and the reduction form will place each state of the form inside this key formbased on the name of the form.
However, this will lead to a strange structure in which the form data for a particular tree is under the form key, and not with other state data associated with it. In this example, the application stores a list of possible types of accounts from the server that should logically be grouped with the registration form itself. However, with the reduction form, they will be in completely different subtrees:
signup
/
forms
/ \
/ login
/
root
\ login
\ /
header
\
signup
I would prefer a more organized tree:
form
/
signup
/ \
/ accountTypes
/
root
\ signinMethods
\ /
login
\
form
?