Add transformQueryKey method to provide custom query key #1811
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t/tanstack-query-custom-query-key
|
|
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
added runtimeConfigPath to tanstack query plugin to support transforming querykey
digistaal
force-pushed
the
feat/tanstack-query-custom-query-key
branch
from
b218303 to
6dad0a3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the query key does not follow the structure recommended by TanStack Query. While most of the times this doesn't give any issues, there are some cases where a hierarichal array is needed. This PR enables a
transformQueryKeymethod to be passed to the plugin via the runtimeConfig file. That gives the flexibility needed to suit all use cases.