DEV Community

Discussion on: What should I do if an operation depends on another first variable

 
fselcukcan profile image
F. Selçuk Can • Edited

Sorry if I repeat; you say even I pass the second argument e.g. [firstVariable] to the useEffect it will still run in the first render eventhough firstVariable did not change.

Additional question:

  • if firstVariable is not same across a rerender but did not cause the rerender, e.g. it is not the cause of rerender since it is not even in the jsx, then the effect will not run. Is that correct?
Thread Thread
 
gsto profile image
Glenn Stovall

Yes, it will run on the first render. It seems a bit odd, but that is how it works. useEffect has to have an initial check, otherwise, how would it know if the variable changed or not?

To your second question, the effect will run, regardless if it was the cause of the rerender. useEffect checks on every render, regardless of the cause.

Thread Thread
 
fselcukcan profile image
F. Selçuk Can

So an effect runs after every render if its dependencies requires so, ie. changed.

I sometimes think guides and docs should be a bit succinct. It is difficult to remember, spot,and find a valueable info in a corner of 5 mins read page.

A gotcha about dependency change is whereas the primitives are regarded not changed after set to same value the arrays and objects are regarded as changed after set to same value, naturally.

Also