Nested models fail when a change/load action is the first action for a model path.

[caesay]

Problem

Given model quote.Applicant.Details.FirstName (text field).

If a rrf/focus action is sent first, the redux state looks like this:

{
    quoteForm: {
        $form: { ... },
        Applicant: {
            $form: { ... },
            Details: {
                $form: { ... },
                FirstName: {
                    focus: true,
                    ...
                }
            }
        }
    }
}

Note here that a $form entry was added at every level of the state.

Now, if a rff/change action is sent first, the model will look like this:

{
    quoteForm: {
        $form: { ... },
        Applicant: {
            Details: {
                FirstName: {
                    value: "",
                    ...
                }
            }
        }
    }
}

Note that $form is missing here at every level except for the top level. Playing with silent, load options yield the same results. At this point the form is now broken and no subsequent actions will create the missing $form fields. Calls to getField for those models (such as quote.Applicant) will now always return the initial state and be inaccurate.

Expectation

I would expect that I should be able to pre-populate any part of my model with a change/load action without breaking things.

[caesay]

For now, the workaround I chose was to set pending = false first prior to the change as this has no other side effects that I can see and causes the state to be created correctly as well.

[davidkpiano]

Is there a reproducible code example you can share? This typically doesn't happen because either:

• the full initial state was provided to the form reducer (e.g., combineForms) which will set up the fields correctly
• all present fields are rendered (e.g., <Control model="...">) which will trigger an initial LOAD action upon mounting.
• both, usually.

[caesay]

For the first point, we have hundreds of fields not all of which are shown initially, they are very conditional so it doesn't make sense for us to pre-populate the store completely, although we do provide some defaults.

For the second point, that's exactly what's happening - we're triggering an initial LOAD when our controls mount, and when this happens it creates the state i described above. If i send a FOCUS or SET_PENDING before the CHANGE action, then things work as expected. I will add a code sample shortly if I can.

[caesay]

Ok @davidkpiano, here's an example, when it loads it will dispatch an action and then dump the state to the textbox: https://codepen.io/anon/pen/WjqRbr
As described - all I do is send a LOAD action and the state breaks.