Making components composable rather than configurable. These are the patterns that stop a component from growing a wall of boolean props.
8 articles
Listed inState ColocationComponent Architectureon
The single highest-leverage state change most apps can make: move it down, and the re-render problem disappears.
Listed inControlled and UncontrolledComponent Architectureon
Who owns the value, why switching between the two warns, and how to support both deliberately.
Listed inCustom HooksComponent Architectureon
Extracting stateful logic so it is testable and reusable without inventing a wrapper component for it.
Listed inHeadless ComponentsComponent Architectureon
Behaviour, state, and accessibility with no markup opinion — you supply the styling and keep the keyboard contract.
Listed inCompound ComponentsComponent Architectureon
Related parts that share implicit state, like a Select and its Options, without threading props between them.
Listed inComposition and ChildrenComponent Architectureon
Passing rendered UI instead of adding another prop — the first answer to a component that has grown twelve options.
Listed inPolymorphic ComponentsComponent Architectureon
The `as` prop, and typing it so the rendered element keeps its own props instead of collapsing to `any`.
Listed inState ColocationComponent Architectureon
Pushing state down to the smallest subtree that needs it, which deletes most re-render problems for free.