-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix(adapter-nextjs): wrong use of nullish coalescing #14112
fix(adapter-nextjs): wrong use of nullish coalescing #14112
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.
Nice catch!
describe('getRedirectOrDefault', () => { | ||
test.each([ | ||
[undefined, '/'], | ||
['', '/'], |
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.
when will empty string be an issue? won't the redirectURL be undefined or expected to be valid?
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.
Empty string is not a valid URI to redirect to. This supplier of the value is the redirectOnSignInComplete
and redirectOnSignOutComplete
parameters on the public API, they are requiring a string
value, so empty string is allowed. As it's not a valid URI so we fallback to the root here, as if it's undefined
.
df2aa27
to
59585f0
Compare
Description of changes
Remove wrong usage of nullish coalescing.
Issue #, if available
Description of how you validated changes
Checklist
yarn test
passesChecklist for repo maintainers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.