feat: maintain reference to refresh-promise to avoid repetitive calls#7
Merged
feat: maintain reference to refresh-promise to avoid repetitive calls#7
Conversation
note: refresh calls are made even if the tokens were updated recently and lock was released recently
paras-fundwave
requested review from
rickygarg
and removed request for
Isha-Sharma
chore: break out of wait-loop @ getAccessToken
rickygarg
approved these changes
Oct 22, 2024
rickygarg
reviewed
Oct 22, 2024
rickygarg
approved these changes
Oct 22, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
store reference to currently ongoing refresh-token network calls to avoid making repetitive calls when
Resolutions
Deployment