jargon

Frontend & browser·State, data and re-rendering

you store each record once by id and keep lists as arrays of ids rather than nested copies.

Normalised state

Also callednormalized state, entity map

Flattening client-side data into a lookup table keyed by identifier, with relationships expressed as ids. It means an update touches one place rather than every list the record appears in, which is what makes editing a shared entity behave. The cost is indirection at read time and a good deal of ceremony, which is why per-query caching has largely replaced it for server data.

Commonly confused with