chore(query-keys): Export SIWEProvider's two query keys, allowing package consumers to invalidate queries
#370
Conversation
This file contains 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
…kage consumers to invalidate queries
|
@jeffrey-computers is attempting to deploy a commit to the Avara Team on Vercel. A member of the Team first needs to authorize it. |
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.
In order to refetch the SIWE session on account change, I need to imperatively trigger a refetch of the
sessionquery in SIWEProvider.tsx.This can be achieved without a const by simply targetting the query key of string "ckSiweSession" - however it is brittle and susceptible to breaking changes.
Exporting these query keys as constants allows package consumers to refetch/manipulate the queries as necessary.