discussion: custom hooks for graphql about query HOT 3 CLOSED

I think this is great! You've proven that the library is flexible enough to be extended or wrapped to handle complex situations. You may want to investigate the custom query key serializers in the docs to take it a step further. Otherwise, I think what you've shown here is sufficiently awesome. There is always a chance that two query key instances may not match up due to implementation, so as long as you're minimizing the risk of that happening, you're in good shape. That's precisely the reason why I added the string + variables approach

from query.

Oh, that's nifty and I indeed missed it (link for others).

I must say that section was a bit scary between the "experimental", "there can be dragons and edge cases", and the thing about "despising the default key". Tbh, I don't despise it, and I'm already fighting the big bad wolf day in day out with my kid, so dragons felt too much to handle ;).

I'll try that some time soon and probably post here again some updated snippets.

from query.

And thanks for taking the time to read through and provide feedback, appreciate it!

from query.