You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using generated hooks, the generated queryKey is always ['string', variables] but it doesn't seem to be a way to change this, for our use case, we would need to pass the fetchParams as part of the queryKey as we send an accessToken that can change.
Describe the solution you'd like
Allow an option in the config to customize the queryKey.
Describe alternatives you've considered
Allow a callback in the generated hook to customize the generated key.
Add a boolean option that passes the dataSource parameter to the queryKey for fetch
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When using generated hooks, the generated queryKey is always
['string', variables]
but it doesn't seem to be a way to change this, for our use case, we would need to pass the fetchParams as part of the queryKey as we send anaccessToken
that can change.Describe the solution you'd like
Allow an option in the config to customize the queryKey.
Describe alternatives you've considered
Allow a callback in the generated hook to customize the generated key.
Add a boolean option that passes the
dataSource
parameter to the queryKey forfetch
Additional context
The text was updated successfully, but these errors were encountered: