-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onRedirectNavigate deprecation fix #7251
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved. Do we have a deprecation notice added that can be emitted on user end?
This is marked as deprecated in the RedirectRequest and if users do set onRedirectNavigate on the RedirectRequest they will get a warning about the field being deprecated and the request not being cached. Let me know if you think we need something further. |
@@ -2740,7 +2747,7 @@ describe("RedirectClient", () => { | |||
await redirectClient.acquireToken(emptyRequest); | |||
} catch (e) { | |||
// Test that error was cached for telemetry purposes and then thrown | |||
expect(window.sessionStorage).toHaveLength(2); | |||
expect(window.sessionStorage).toHaveLength(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This (and line 3335 below) are reverting a change that was wrongly made in the redirect retry PR.
This PR has two fixes: