github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1557] Ability to set "name" and any "additionalFields" when signing-up through authClient.signIn.emailOtp #8817

New Issue
Closed
opened 2026-04-13 04:01:59 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-13 04:01:59 -05:00
Owner
Copy Link

Originally created by @PitonsSkipper on GitHub (Feb 24, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1557

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Currently authClient.signIn.emailOtp can only handle email, and otp in the object.

authClient.signIn.emailOtp could either inject in the same payload the additionalFields and "name" which is a already existing field in the Users table, or add a extra object in the function to carry those values.

Describe alternatives you've considered

This allows to not call authClient.updateUser right after OTP verification.

Additional context

No response

Originally created by @PitonsSkipper on GitHub (Feb 24, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1557 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like Currently `authClient.signIn.emailOtp` can only handle `email`, and `otp` in the object. `authClient.signIn.emailOtp` could either inject in the same payload the additionalFields and "name" which is a already existing field in the Users table, or add a extra object in the function to carry those values. ### Describe alternatives you've considered This allows to not call `authClient.updateUser` right after OTP verification. ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:01:59 -05:00
GiteaMirror commented 2026-04-13 04:02:02 -05:00
Author
Owner
Copy Link

@ycherabai commented on GitHub (Mar 22, 2025):

+1

<!-- gh-comment-id:2745372545 --> @ycherabai commented on GitHub (Mar 22, 2025): +1
GiteaMirror commented 2026-04-13 04:02:03 -05:00
Author
Owner
Copy Link

@thecoorum commented on GitHub (Apr 9, 2025):

+1

<!-- gh-comment-id:2790918453 --> @thecoorum commented on GitHub (Apr 9, 2025): +1
GiteaMirror commented 2026-04-13 04:02:04 -05:00
Author
Owner
Copy Link

@diogosarti commented on GitHub (May 19, 2025):

+1

<!-- gh-comment-id:2891533728 --> @diogosarti commented on GitHub (May 19, 2025): +1
GiteaMirror commented 2026-04-13 04:02:05 -05:00
Author
Owner
Copy Link

@jelil-iSelect commented on GitHub (Jul 28, 2025):

+1

<!-- gh-comment-id:3126884005 --> @jelil-iSelect commented on GitHub (Jul 28, 2025): +1
GiteaMirror commented 2026-04-13 04:02:06 -05:00
Author
Owner
Copy Link

@filipe942 commented on GitHub (Oct 15, 2025):

+1

<!-- gh-comment-id:3405904609 --> @filipe942 commented on GitHub (Oct 15, 2025): +1
GiteaMirror commented 2026-04-13 04:02:06 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Oct 15, 2025):

this should be fixed by 1.4

<!-- gh-comment-id:3406030815 --> @ping-maxwell commented on GitHub (Oct 15, 2025): this should be fixed by 1.4
GiteaMirror commented 2026-04-13 04:02:07 -05:00
Author
Owner
Copy Link

@idonov commented on GitHub (Oct 22, 2025):

+1 status?

<!-- gh-comment-id:3434378534 --> @idonov commented on GitHub (Oct 22, 2025): +1 status?
GiteaMirror commented 2026-04-13 04:02:08 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Oct 24, 2025):

@idonov it should be fixed by version 1.4, keep an eye out for when the release comes.

<!-- gh-comment-id:3441472215 --> @ping-maxwell commented on GitHub (Oct 24, 2025): @idonov it should be fixed by version 1.4, keep an eye out for when the release comes.
GiteaMirror commented 2026-04-13 04:02:08 -05:00
Author
Owner
Copy Link

@idonov commented on GitHub (Nov 23, 2025):

@ping-maxwell I see 1.4.1 is out, what is the recommented way to sign up users with otp now?
I don't see a 'name' property in the signIn.emailOtp method, nor a signUp.emailOtp.

<!-- gh-comment-id:3568190770 --> @idonov commented on GitHub (Nov 23, 2025): @ping-maxwell I see 1.4.1 is out, what is the recommented way to sign up users with otp now? I don't see a 'name' property in the signIn.emailOtp method, nor a signUp.emailOtp.
GiteaMirror commented 2026-04-13 04:02:09 -05:00
Author
Owner
Copy Link

@Diogomartf commented on GitHub (Dec 22, 2025):

+1

would love to have this

<!-- gh-comment-id:3682665995 --> @Diogomartf commented on GitHub (Dec 22, 2025): +1 would love to have this
GiteaMirror commented 2026-04-13 04:02:09 -05:00
Author
Owner
Copy Link

@berteotti commented on GitHub (Dec 26, 2025):

+1

important to have "additionalFields" for us

@ping-maxwell what's the status here?

<!-- gh-comment-id:3692704749 --> @berteotti commented on GitHub (Dec 26, 2025): +1 important to have "additionalFields" for us @ping-maxwell what's the status here?
GiteaMirror commented 2026-04-13 04:02:10 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 1, 2026):

This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.

<!-- gh-comment-id:4166560438 --> @github-actions[bot] commented on GitHub (Apr 1, 2026): This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8817
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?