SebastianVerified account

Sorting props/type members alphabetically (My team enforces this via lint and it drives me nuts)

I like rules like this but only when used in conjunction with a lint autofix.

Components which pass properties to child components which pass properties through to child components which pass properties through to child components which pass properties through to child components which pass properties through to child components which pass properties throu

If those props "make sense" for intermediate layers of components, nothing wrong with passing them deeply down

Copy props to state. Most of the time you can lift the state up.

16.3 will have official way to do this via `static getDerivedStateFromProps`. It works like memoization.

Overeager modularization, people often hide 2 lines of rendering logic and 5 dom attributes across 10 files that just render a simple ul/li used in exactly one location then will chastise you for using setState because it's not functional programming

Splatting out more props than needed onto a child element. Splatting incoming props on multiple child elements.

Yes! This is dangerous for so many reasons. Re-rendering repeatedly for unused props, event handlers firing repeatedly, messed up styles, the list goes on.