fix[okta-react]: add missing await on restoreOriginalUri#283
Closed
nhardy wants to merge 1 commit into
Closed
Conversation
Fixes an issue where restoreOriginalUri returns a Promise that is not awaited on by oktaAuth.handleLoginRedirect()
Author
|
Resolved in #284 |
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
1 participant
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently when providing a
restoreOriginalUrifunction that returns aPromiseto the<Security />component, this promise is not awaited on inoktaAuth.handleLoginRedirect(). This means that relying on the resolution of theokta.handleLoginRedirect()promise does not reliably indicate that the redirect has completed.Issue Number: N/A
What is the new behavior?
If
restoreOriginalUrireturns a promise, it will be awaited when callingoktaAuth.handleLoginRedirect().Does this PR introduce a breaking change?
Other information
Reviewers