Why react query plugin doesn't generate hooks?

[nutrian]

Why doesn't the react query plugin generate hooks like useGetEndpointQuery or usePostEndpointMutation ?

Components require two imports useQuery or useMutation in addition to the generated getEndpointOptions

It would be nice to import just useGetEndpointQuery(options) or usePostEndpointMutation(options)

[mrlubos]

Hi @nutrian, it's honestly a preference. Feel free to open this as a feature request! To answer your question why though, the current output "forces" you to use the native TanStack APIs as opposed to completely abstracting them.

Your request makes total sense though, there might be people who prefer to abstract the whole hook. I'm not sure how many people prefer this syntax, we will find out soon. The only question I'd have is around the hook API, since we still want to allow you to customise each request with Hey API-specific options. I'm assuming we'd be adding another parameter to the function, curious if you have any thoughts on that?

[lucsky]

I used to completely abstract the entire hooks too, but for the wrong reason, aka aesthetic. I am now declaring all my queries (using queryOptions, see https://tkdodo.eu/blog/the-query-options-api) and mutations like the RQ plugin does because it is way more flexible, and imho the way it should be.

It allows to:

• access the query key directly, which can be useful for post mutation invalidations
• access the query function directly, which can be useful for imperative calls or to pass to other RQ APIs like QueryClient.ensureQueryData, for example.
• and more...

[lucsky]

Just to be clear, what I'm saying is that wrapper hooks can be nice and can provide nice DX, no question about that, but that adding them (if ever) should be in addition to the core queries and mutations definitions, which give the maximum flexibility (at a cost which I personally consider pretty minor).