Fixed deeply dynamic model support

[kabbi]

This fixed the case when the model dynamically changes in the middle of the chain - for example, you were using deep Fieldset hierarchy, and any of them had dynamic model
The problem is caused by the fact that resolveModel decorator, that is used internally to allow partial models, was caching model value upon mounting, thus preventing it from updating properly.
I've also removed several performance optimizations, as they were also preventing context updates. I'm open to any way this could be done better.

[davidkpiano]

I'll have to see how performance is affected with this. Can you elaborate more in how exactly the performance optimizations were preventing context updates? Maybe we can work around it without sacrifices.

[kabbi]

The intermediate component you've created, DefaultConnectedControl, does not know anything about contexts that are used by resolveModel. So we can't check if it is updated, and restrictive shouldComponentUpdate implementation would block the context propagation, leaving Controls with an old model value.
Some kind of related discussion can be found here: facebook/react#2517.
I can declare contextTypes on DefaultConnectedContol though, and then check if they've updated in shouldComponentUpdate. But it seems hacky for thic component to know anything about context props used in resolveModel.

[davidkpiano]

I can declare contextTypes on DefaultConnectedContol though, and then check if they've updated in shouldComponentUpdate. But it seems hacky for thic component to know anything about context props used in resolveModel.

That might be an idea. The reason for resolveModel is that React-Redux's connect() doesn't know anything about context, unfortunately. If it did, that would fix the issue, as we can do resolved model-checking logic in there.

[davidkpiano]

Looks good, thanks for adding the sCU logic back in!