Hacker News Reader

Parent Full thread

fastball

I don't really understand extendState because it seems like somewhat pointless syntactic sugar for:

setState((previousState) => ({...previousState, foo: false}))

View on HN

I would imagine it would help more with nested objects.

({ contact: { address: "" } })

as opposed to

({ ...prev, contact: { ...prev.contact, address: "" } })

I guess how you should handle that is ambiguous. Probably best to be explicit for that reason.

For deeply nested data, I would probably use `immutability-helper`. Many deep spread operators can get ugly and confusing pretty quickly, in my experience.

Yep! It is syntactic sugar. I personally like it though because it results in slightly cleaner, more concise code. It's just easier on my eyes.

Normally syntactic sugar is fine and has a near-zero cost, but in this case I don't think that's actually true.

Given the way hooks are structured, if I want to use both `setState` and `extendState` in a `useCallback`, I'd need to pass both to the dependency array, which is just extra effort (which defeats the purpose of the syntactic sugar imo).

Reply on news.ycombinator.com