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.
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
feat: replace redirect url pattern with route key pattern #398
base: main
Are you sure you want to change the base?
feat: replace redirect url pattern with route key pattern #398
Changes from all commits
13d8848
c123713
097298d
035ac17
bd0228d
d97cb95
8ed0be6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
seems like this will redirect to
HOME
instead? is that intended?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.
The component redirects to
/sign-in?callbackUrl=<redirectTo>
when not signed in,redirectTo
defaults toHOME
if not provided.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.
i wonder if this would work for dynamic routes (like
/user/[userId]
). If not, might break many autoredirects/ cause confusion.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.
No it doesnt, it will definitely break dynamic routes.
The issue is because
router.push
does too much magic (e.g. you can dorouter.push('/home/[x]?x=../signout')
to/signout
)It became quite challenging to validate that
router.push
does not cause unintended navigation with user supplied input (?callbackUrl
param) (especially across next versions), so the alternative is to use a hardcoded whitelist approach like the PR shows.appUrlSchema
can still be used to validate urls if the dev wishes to use dynamic urls, just that the additional friction is supposed to discourage thatThere 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.
Happy to hear about alternatives though, not sure what's the best approach tbh