observeProps surprising behavior about recompose

[dralletje]

This is actually a problem from lifecycle(). Lifecycle() runs the setup function in the constructor, which is, I guess, in Reacts perfect world a pure function as well (only setting state once). Calling the constructor becomes 'part of' the render function of the parent component, so something that calls .setState() in a constructor is considered an error (impure render function). For that reason, observeProps doesn't call .setState() till it is rendered, but uses .state = ... instead. This, however, does not trigger a rerender, thus you'll end up with old state.

Either lifecycle has to be altered to trigger in componentWillMount() ( @acdlite what is the reason it is on the constructor right now? ) or you should move the fetching/not fetching into the observeProps() function itself :-)

[acdlite]

Closing because we got rid of lifecycle().