[React 16] Bug: true and false clauses being rendered simultaneously about react

[ppaul]

I wouldn't worry to much if you could only see the comments. If you have also duplicate markup, that would help. Otherwise, the root cause can be in 1000 places that determine rendering

[pedrobernardina]

If you have also duplicate markup, that would help.

Hi @ppaul . Could you elaborate what is needed? I'll try to provide it.

[ppaul]

I think I misunderstood. So, seeing those twice does that mean the component rendered twice? I suggest rewriting the jsx for debugging purposes and console log on each case. I see you use provider (and probably context). Do you know, react warns that context might lead to unnecessary renderings and people also complain about:
"What is wrong with using context in React?
React Context is often used to avoid prop drilling, however it's known that there's a performance issue. When a context value is changed, all components that use useContext will re-render." (stackoverflow). Try to see what caused the render.

[pedrobernardina]

I'm not sure if it's rendering twice. To be honest, I don't know how to phrase this problem. What's happening is that both true and false clauses are being returned at the same time.

I'm having a hard time reproducing it now, but I'll test different scenarios to try gathering more evidence .

[JSerZANP]

<!--$--> is the marker for Suspense in Server side rendering.
Maybe there are some issues in the hydration process, but I'm not sure what is going on unless I see the code that repros.

[pedrobernardina]

<!--$--> is the marker for Suspense in Server side rendering. Maybe there are some issues in the hydration process, but I'm not sure what is going on unless I see the code that repros.

Hi, sorry for the late reply.

This code is built and run on a cloud framework, and we have no access of it's internal processes. Is there anything that I could provide you that would help?