chore(Authorization)!: Updates Token Storage Structure #400
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.
{CLIENT_ID}:{RESOURCE_SERVER}.AuthorizationManager.getGlobusAuthToken()andAuthorizationManager.hasGlobusAuthToken()have been deprecated; UseAuthorizationManager.tokens.authinstead.authenticatedevent no longer provides atokenas part of the event payload. Originally, this would only provide the Globus Auth token, but your application might never require a Globus Auth token (and only tokens from a specific service).This has been marked as a breaking change based on the structure change to how tokens are stored; This would only be a breaking change if you are accessing stored tokens in
localStorageorsessionStoragedirectly, which is not advised (use theTokenManagerinstance instead).