github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #3677] [CLOSED] Enforce required 'name' field for email/password signup (Fix #3336) #21852

New Issue
Closed
opened 2026-04-15 20:39:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 20:39:13 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3677
Author: @Nitish-Naik
Created: 7/28/2025
Status: ❌ Closed

Base: main ← Head: issue-3336-require-name-signup

📝 Commits (1)

📊 Changes

1 file changed (+13 additions, -0 deletions)

View changed files

📝 packages/better-auth/src/api/routes/sign-up.ts (+13 -0)

📄 Description

The backend previously allowed users to sign up with only email and password, even though the documentation specifies that the name field is also required. This PR updates the backend validation to enforce that the name field is mandatory for email/password signups, ensuring consistency between the implementation and the documentation.

Fixes #3336.

Summary by cubic

Enforced the 'name' field as required for email/password signups to match documentation and prevent incomplete registrations.

  • Bug Fixes
  • Added backend validation to reject signups missing a name.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/3677 **Author:** [@Nitish-Naik](https://github.com/Nitish-Naik) **Created:** 7/28/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `issue-3336-require-name-signup` --- ### 📝 Commits (1) - [`b6ee48c`](https://github.com/better-auth/better-auth/commit/b6ee48c3aa86233955a3f53f796e545d1c2ae09d) fix: name require signup ### 📊 Changes **1 file changed** (+13 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/api/routes/sign-up.ts` (+13 -0) </details> ### 📄 Description The backend previously allowed users to sign up with only email and password, even though the documentation specifies that the name field is also required. This PR updates the backend validation to enforce that the name field is mandatory for email/password signups, ensuring consistency between the implementation and the documentation. Fixes #3336. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Enforced the 'name' field as required for email/password signups to match documentation and prevent incomplete registrations. - **Bug Fixes** - Added backend validation to reject signups missing a name. <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 20:39:13 -05:00
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 pull-request
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#21852
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?