Use validateToken to exchange refresh token in OAuth getFetcher #3750
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.
One tiny bugfix in this (was missing a "$" in a template literal substitution). Feel free to cherry-pick that commit out if the other commit requires more discussion.
Side note, it seems like there should be some sort of eslint rule that warns about
{
instead of${
in template literals, but the closest thing I could find was disallowing backticks unless they contain a substitution or a newline:The other commit is something where when I was reviewing #3742 I kept feeling like I'd tried to do something similar before, and I finally remembered what it was. It's possible to use
validateToken
to accomplish what I think is the same thing usinggetPreAuthorizationInformation
does, which is basically making sure the refresh token for something that doesn't use RPC gets exchanged correctly. It seems to work fine in my testing.I thought it might be a bit less confusing since
getPreAuthorizationInformation
was originally created specifically for RPC, so calling it in the main thread might be counterintuitive.