state is treated like observable and calls componentWillReact every change

[rlesniak]

I found this issue while update from 3.5.9 to 4.0.3

Reproduced here: JSBin (play with mobx-react version in HTML tab)

On older version mobx-react was calling componentWillReact only once - when I change observable value. Now its calling every time I do setState in my handleChange event. 3.5.9 didnt have this behavior.
I treat this like a bug because I didn't mark my state as observable so mobx should not treat it like observable.

But if its a feature ( ͡° ͜ʖ ͡°) then plase help me with bringing back my target behavior without rollbacking version. Thanks.

[Strate]

This was made as a feature together with #124.
As for now, both props and state are observables. Do you really need that granular discrimination between state reaction and obervable reaction? Because your component actually has a re-render of state changed, and now you can use your state in computed properties.

If you need to do something only on blur, why just not to do it onBlur?

[rlesniak]

All right, I found workaround, I use reaction instead of my previous solution.

Maybe you should update README because now there is misleading info:

componentWillReact won't fire when receiving new props or after setState calls (use componentWillUpdate instead)

but it is not true anymore since 4.0.0. I am right?

[Strate]

@rlesniak I suggest you to use computed for parsed number and 2nd observable variable, which sets on blur and used in calculation of computed variable. Then you do not need to use reaction.

[Strate]

@rlesniak I've changed the readme, so, gonna to close this issue. Feel free to reopen if you have any questions left.