observer component re-renders even though observed value doesn't change about mobx-react HOT 4 CLOSED

@bengry it depends, if things of the observed by the computed change, the computed has to recompute, if it than concludes it didn't produce a different value than before, it won't propage further, etc.

from mobx-react.

from mobx-react.

@bengry The View component don't re-render although the trace is printed. The log of [mobx.trace] only remind that the reaction maybe run agin(see trace code).The reaction doesn't rerun if it's dependencies are not changed(see shouldCompute).

from mobx-react.

In your example someProp isn't read by the computed, but by the component. The struct only works if you create non-observable data structures in your computed.

Now that you mention it, it does make sense. Is it mentioned in the docs that you need to read the individual values? In my real-world scenario I ended up doing a spread on the params, which should work just as well, for any number of properties on the _params object. Please correct me if I'm wrong here though.

@bengry The View component don't re-render although the trace is printed. The log of [mobx.trace] only remind that the reaction maybe run agin.

I stand corrected, I just put a console.count in there and it does indeed not called 👍.
Good to know that a trace() log does not necessarily mean a re-computation. Is that also true for other stuff (i.e. a trace() inside a computed that depends on another observable (or a computed which at the end derives from one..). i.e. the dependant computed won't be re-evaluated even though the trace() placed inside of it is printing?

from mobx-react.