CredentialManager: add hasValidRefreshToken() method #701
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
Without this, there's no synchronous way to tell if the stored credential can be refreshed, even if `isValid()` returns false.
|
Hi @AndrewSB , thank you for the report but we're missing some important information. Please re-open a new PR with a completed PR template. Delete sections that are not relevant, ask for help for sections that are not clear, and check all required checkboxes. Please explain your use case for this feature in detail as well. |
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.
Version 2.0.0 of the SDK dropped checking for refresh tokens (#574)
Without this, there's no synchronous way to tell if the stored credential
can be refreshed, even if
isValid()returns false.