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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fixed tokens initialization. Fixed SendModal for ENS. #9330
fix: Fixed tokens initialization. Fixed SendModal for ENS. #9330
Changes from all commits
8ee81f8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@igor-sirotin
The original way assigned a value to the table without updating the timestamp, so whatever value we set will be considered "old" and
isCached
will return false immediately. If the user requires "fresh" values, they'll need to be fetched.In the new way, calling the
set
method will update the timestamp, so the values will be considered "fresh" andisCached
will returntrue
for whatever duration is used, which is wrong since the values we used to init will probably be quite old.I think the other changes should fix the issue and this one should not be necessary. I'll revert this change in a new PR and test to see that everything's still working fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually this was the first place the app crashed 🙂
Because
self[cacheKey].value
was setting value of non-existable-in-table element.But maybe I remember something wrong, check it out