-
Notifications
You must be signed in to change notification settings - Fork 331
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(nextjs): Support auth().redirectToSignUp()
#5533
base: main
Are you sure you want to change the base?
feat(nextjs): Support auth().redirectToSignUp()
#5533
Conversation
🦋 Changeset detectedLatest commit: b31e524 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
const targetUrl = signUpUrl || accountsSignUpUrl; | ||
|
||
// Allows redirection to SignInOrUp path | ||
function buildSignUpUrl(signIn: string | URL | 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.
Just want to make sure that I understand this part here. If there's a sign in URL option (env var or middleware key), we assume that combined flow is enabled - but doesn't it also need be able via the withSignUp
prop?
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.
yes, but in that case signUpUrl will be defined. withSignUp
is per component, nothing in can do about it on the server.
Co-authored-by: Laura Beatris <[email protected]>
Description
Original PR.
This PR simply removes duplicated code and improves the changeset example.
Checklist
pnpm test
runs as expected.pnpm build
runs as expected.Type of change