jargon

Frontend & browser·State, data and re-rendering

two sibling components needed the same value, so you moved it into the parent they share.

Lifting state up

Moving state to the closest common ancestor of the components that need it, and passing it back down. It is the standard fix for two components that must agree, and it is what turns a component into a controlled one. The cost is that the ancestor now re-renders on every change, taking its whole subtree with it unless something below is memoised.

Commonly confused with