feat: Refresh cached data when transaction is sent/confirmed #11
+1,656
−289
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
This is necessary to make sure that transaction lists are updated when a new one is sent. By invalidating the queries, the transactions are refetched and replace the ones in the cache. Add `useAddress` hook and use it instead of the `useSafeInfo` when only the address is needed. Move the queryClient and invalidateQueries functions to a new file called queryClient.ts for better organization and separation of concerns.
Create individual hooks for each Safe Info prop
Yarn link the unpublished types-kit package
Fix the yarn link command
Checkout the safe-core-sdk at the commit hash before types-kit was introduced
Pull Request Test Coverage Report for Build 10998049945Details
💛 - Coveralls |
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.
When a transaction is executed or confirmed, the cached data is updated. This is done by invalidating the corresponding queries which makes the data being fetched again and replacing the cache.
Additionally the
useSafeInfohook is refactored, by moving the individual properties (address, threshold, owners, nonce, isDeployed) into separate hooks. That way, we can internally use those individual hooks, instead of fetching all the data.