The useHook with selector does not trigger rendering properly

[bcytrowski]

The useHook with selector does not trigger rendering properly

[anacierdem]

This is by design. See the selector docs here as well. The output of the selectors undergo a shallow equality check. I also missed this previously when I opened this issue and proposed that maybe exposing the equality function might be useful. On the other hand at this point I'm pretty much convinced that keeping it opinionated is safer for the health of the library.

[albertogasparin]

From a dev expectation pov, 99% of the times selectors returning same data wrapped in a different object instance mean nothing has changed. So a re-render is pointless. I understand that there might be cases where this behaviour is unwanted, but the workaround is fairly simple and cheap (as you described, just add a nested object) that I feel expanding the API has not much value.
However if you feel like docs should make a better job highlighting this behaviour, I welcome suggestions 😉

[bcytrowski]

I totally agree with you guys - I just shared my observations of a dev coming from redux/reselect world. I believe aligning the current behavior with react-redux useSelector would be a breaking one. I'm totally fine with the outcome of this thread and the workaround is perfect for me :) Thanks