Using react-redux connect deep force update does not work

[haneev]

forceUpdate is ignored by react-redux connect. Because internally a renderedElementis stored and forceUpdate does not reset this element, leading to rendering an possibly 'old' component. A fix could be like adding this code to deepForceUpdate. Or update react redux connect to handle forceUpdate.

    traverseRenderedChildren(node, internalInstance => {
        const instance = internalInstance._instance;
        if (instance && instance.renderedElement) {
            instance.renderedElement = null;
        }
    });

[gregberge]

I think it is possible to trick it using #6 isn't it?

[wmertens]

I think I'm making it work by using

					deepForceUpdate(
						this.childRef,
						// Deep react stuff - the stateNode is probably from react-hot-loader
						instance => {
							const n = instance && (instance.stateNode || instance)
							return n && (n.context && n.context.i18n)
						},
						instance => {
							const n = instance && (instance.stateNode || instance)
							if (n && n.updater && n.updater.enqueueForceUpdate)
								n.updater.enqueueForceUpdate(n)
						}
					),

i18n is the context I'm updating, the stateNode is probably from react-standin, and the enqueueForceUpdate is some voodoo API from somewhere, possibly React?.

This is using v4 beta btw.