Thomas Roch
Thomas Roch
You can compose `routeNodeSelector` with your `mapStateToProps`. The proper way to use `routeNodeSelector` is as a thunk, otherwise memoization won't work properly. ```js const mapStateToProps = (state) => { const...
`routeNodeSelector` is a memoized selector which only returns a new value (routing state) if the provided node name (in your case `'user'` is concerned by a route change. Your code...
Also I imagine you have another route node selector (or component bound to the route) above your `routeNodeSelector('user')`?
If the payload is undefined, it shouldn't crash for sure. I think console logging an error would be enough?
Hello, I've been following this issue as when it was initially created, we had been started to use tRPC and try to get rid of nestJS / graphQL. For websockets...
Hi @mrzepinski, Sorry for being so late to come back to you. Your change is a good addition, however I don't think the option name `optionalQueryParams` is the best: query...
Should be fixed with version 0.2.2
:+1: looks nice
> Only reason I was hesitant to add it was that you can get the same thing with memoization, which is more 'standard' than something like this. 100% agree
I think the problem with memoizing is universal apps.