@ryanflorence@KokoChris_dev Going to dig this up, but while the remix request invalidation is fantastic, is the only option to put all of those extra requests onto the server?
It's a lovely user experience, but the CPU/memory/bandwidth graphs surely go up quite a bit?
@TkDodo I discovered this today, and you probably already know, but when you open the Components tab in dev tools, you can view the hooks and their indexes.
Whether that's helpful is another matter!
@mattpocockuk I'd be really keen to see your full example of this. We have a big complicated one which handles 'optimistic' state, as we found the search params causing the whole page to update on every tick was too much
I have a question @mattpocockuk: I know enough about generic to grasp what I'm doing wrong, but not enough about how to fix it. Please help!
https://t.co/x1zZohHT7a
@Rishabh8Singh@housecor@TkDodo@_georgemoller@bobziroll You're right in that it's not making a new function each time, but it's often worth avoiding passing function references around as the implicit arguments passed in can be the cause of subtle bugs. What, for example, would happen if your function started using an argument?
@PipoPeperoni@TkDodo@ryanflorence@aazarkhish There was the middleware RFC, and I asked the same question on that, but it looks like it's been superseded by the new V3(?) stuff?
https://t.co/QHgKzkXCZo
@TkDodo I found out what it was - I'm relying on multiple indicators as to whether a query should be run. The 1st is whether it's valid to run (skipToken) and the 2nd is at the observer point where something else has an opinion:
https://t.co/iUVfo1LdsK
Any advice on a better method?