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
Currently, the implementation has a potential issue because useQuery calls from different clients are assigned the same key, even though they're querying different endpoints.
Here, both queries receive the same key, even though they are querying different sources.
... and remove options parameter
Currently queryOptions spreads the options parameter in the last argument. It might be cleaner to make this the library user's responsibility, as shown in the following examples, which yield the same result but simplify the implementation:
Description
I'm referring to these lines.
Add client parameter to
queryKey
Currently, the implementation has a potential issue because
useQuery
calls from different clients are assigned the same key, even though they're querying different endpoints.For example:
Here, both queries receive the same key, even though they are querying different sources.
... and remove
options
parameterCurrently
queryOptions
spreads theoptions
parameter in the last argument. It might be cleaner to make this the library user's responsibility, as shown in the following examples, which yield the same result but simplify the implementation:Proposal
The title summarizes the changes.
Checklist
The text was updated successfully, but these errors were encountered: