Alternative to forceUpdate about mobx-react HOT 5 CLOSED

No, just testing / reading sources / reverse engineering. It is just that setState, schedules, where forceUpdate executes. Sinces MobX already schedules, it is the better fit that avoids doing similar administration twice and avoids triggering unrelated lifecycle hooks. I hope that clarifies!

from mobx-react.

@arahansen, this.setState({}) would indeed result in rerendering, but then there is no guarantee, that it happens synchronously, so that mobx is able to derive reactive values, used during rendering.

from mobx-react.

indeed, forceUpdate is used internally, but it is behind MobX own scheduling mechanism, which is even more optimal then Reacts own setState mechanism. So as a component developer you shouldn't use it, but it is a perfect low level primitive where libs like mobx-react can build upon

from mobx-react.

Interesting, I was not aware of this!

Do you have any related studies or information on how forceUpdate is a preferred primitive for building libraries?

from mobx-react.

Yes, thanks for the explanation!

from mobx-react.