Selectors? about unstated-next HOT 3 CLOSED

"selector" is designed for solo-store solutions like redux, since they need to avoid rerendering for unaffected nodes.

For multi-store case, you'd better have another container if these states are irrelevant.
To prevent unexpected rerendering, check memo or useMemo.
As well you can expose the setter/reducer of one store so you can dispatch the actions, triggered by the change of another store state, inside your component logic

from unstated-next.

There do seem to be some solutions about using only part of what useContext returns in this comment.

from unstated-next.

I see that there's documentation in the README for this, under the "Optimizing components" section. Was that not there before, or did I miss it earlier? 😅
Anyway, closing this then.

from unstated-next.