-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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: allow to disable client-side redirect for email provider #1379
feat: allow to disable client-side redirect for email provider #1379
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/6PEz5qJMjSTmUuWXkL39XfQV149n |
3a73215
to
857017b
Compare
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.
Thanks! Will check the functionality locally myself, until then, there is a little request. Could you update the docs at https://github.com/nextauthjs/next-auth/blob/main/www/docs/getting-started/client.md#using-the-redirect-false-option
to mention that redirect can also be disabled for the email provider from now on?
@balazsorban44 I've updated the docs |
Sorry for the late discovery, but this should have been opened against the |
@balazsorban44 Here you go: #1416 |
What:
In case the user is using the Email provider, make it possible to disable the redirection after the response from the server.
Why:
Example: To make a user signin or signup flow more fluid, it may be desirable to handle email signin without a page reload.
How:
The Email Provider has been added to the list of the providers that allow disabled redirection
canRedirectBeDisabled = isCredentials || isEmail
Checklist:
Also related: