Refactor double-fetch for token changes #212
Merged
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.
Previously we would perform a
getIdTokenResult()
, followed by agetIdToken()
call. This is two API calls to Firebase, and can be simplfied by using thetoken
property from the resutl ofgetIdTokenResult()
.Also updates the
onIdTokenChanged
flow to handle errors more gracefully, byreturn
ing early if we are unable to retrieve the token details (rather than settingnull
data to memory.Observing the source of
getIdTokenResult
athttps://github.com/firebase/firebase-js-sdk/blob/6d31930b3abe1588ae81a5c14b59cd386fddc718/packages/auth/src/core/user/id_token_result.ts#L55-L88 it is evident that it calls
getIdToken
internally.See https://github.com/firebase/firebase-js-sdk/blob/6d31930b3abe1588ae81a5c14b59cd386fddc718/packages/auth/src/core/user/user_impl.ts#L102-L116 for the original
getIdToken
source.