Call all functions twice in StrictMode

[eps1lon]

React version: 16.3-16.13

Steps To Reproduce

1. Render function component with side-effects and without hooks in StrictMode
2. Component only renders once

Link to code example: https://codesandbox.io/s/strictmode-w-and-wo-hooks-vgxvh

The current behavior

StrictMode only renders function components with hooks twice following #15074 (comment)

The expected behavior

I think making the distinction between components with and without hooks causes more confusion than it helps. Especially since the docs do not mention this. I amended past efforts to improve the StrictMode docs but since this has been ignored I'm not sure this helps. I would also work on making the behavior consistent across all function component types if this is possible.

[gaearon]

Yeah I think it would be reasonable to flip it for all functions. Happy to take a PR doing that.

[gaearon]

since this has been ignored I'm not sure this helps

Would you like to volunteer maintaining the docs? Tbh we're a bit swamped by all the other work right now and this would be helpful.

[bvaughn]

I think this proposed change makes sense in regular DEV usage, but wrt tests, it's probably worth discussing the reason we didn't do this in the first place:
#14639 (comment)

This change might be observable in a way that breaks existing tests (e.g. if I mock a module/component and then assert on the number of renders). Not sure how common this is, and also– I think this change might still be the right thing to do in a minor. Just seemed worth considering.

Just look at our own tests to see lots of special handling for double rendering and expecting yielded values.

That being said, maybe there aren't many pre-existing tests that are in strict mode, so maybe this is still the right trade off- but I expect we'll get some negative push back from this change.

[eps1lon]

Would you like to volunteer maintaining the docs?

Sure. I can probably dedicate an hour or two per week.

we'll get some negative push back from this change.

I'm not so sure about it either. We had this only come up because we also publish a hook as a higher-order component and the user (and I) were confused why one would render twice while the other didn't.

However, I hope it's easier to justify that StrictMode renders twice than explaining why it only renders twice in certain situations. Maybe it's even better to have it appear like render-count is non-deterministic? 😄

[gaearon]

I think let's try to sync to WWW and see how much this breaks. I think there is an argument that if you're counting different method calls, we've already changed that for sCU recently, so there is a precedent.

We "break" tests that assert on console calls when we add new warnings, but that's a part of our policy. I think this is similar. Additionally, the number of renders isn't even deterministic in general. Our bailout heuristics can, and will, change too.

[jyash97]

Hey @gaearon @bvaughn just checking if it will be a good way to let developers know about the extra rendering in form of console warning when strict mode is enabled.

I have seen many developers ask the same question on Stackoverflow and on Github issues. How about a warning like this:

StrictMode will intentionally double-invoke render, constructor, etc to detect side effects. Read more [here](https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects) 

Thoughts ?

[gaearon]

This will just be annoying noise IMO. If a mode produces more logs even when everything is good, people will turn it off to reduce the noise.

[gaearon]

I have seen many developers ask the same question on Stackoverflow and on Github issues

Eventually there'll be enough answers for them to come up in results and people will stop asking. :-)

[jyash97]

This will just be annoying noise IMO. If a mode produces more logs even when everything is good, people will turn it off to reduce the noise.

Yeah I agree on this behavior, I did not think in this direction.

I have seen many developers ask the same question on Stackoverflow and on Github issues

Eventually there'll be enough answers for them to come up in results and people will stop asking. :-)

Haha true, doing the same by guiding people.

Thanks for the quick reply and sharing your thoughts :)