fix(cache): Exclude custom assets from cache retrieval logic FE-1122 #1710
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
nelitow
requested review from
luizstacio,
LuizAsFight,
helciofranco,
arthurgeron and
rodrigobranas
as code owners
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.
Custom assets when added or updated required a page reload or a 5 minutes timeout to be updated in the wallet.
By excluding these custom assets from the cache, they are refetched locally instantly whenever the user adds or updates the asset data.
As this is not a network request, a simple local refetch should not affect performance.
Before:
https://github.com/user-attachments/assets/573f3d9c-64c2-4e25-8650-3bbb997e42ae
After:
https://github.com/user-attachments/assets/e027e4ec-bffa-4a3d-b8d3-66da3bda1713