Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Children are rendered in the wrong order
See original GitHub issueAfter a child component’s render() method returns null, any subsequent renders cause the component to render in the wrong order.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Children rendered in the wrong order unless both of them are ...
The order of components should be stable even after any of them returned null . Actual Behavior. The order is not stable.
Read more >Problems reordering child components from parent's state
However, when I try and reorder the objects in the array (to change the order of the children in the DOM), it changes...
Read more >The mystery of React Element, children, parents and re-renders
Children are not children, parents are not parents, memoization doesn't work as it should, life is meaningless, re-renders control our life ...
Read more >React Children And Iteration Methods - Smashing Magazine
In this article, we'll discuss and learn about the use case of iterating over React `children` and the ways to do it. In...
Read more >Composition vs Inheritance - React
React has a powerful composition model, and we recommend using composition instead of inheritance to reuse code between components.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Most likely #581?
We can leave it open, I think over half of the open issues right now are fixed in 8 haha.