Skip to content

Show specific password requirements on signup#20

Merged
xaelophone merged 1 commit into
mainfrom
fix/signup-password-requirements
Feb 24, 2026
Merged

Show specific password requirements on signup#20
xaelophone merged 1 commit into
mainfrom
fix/signup-password-requirements

Conversation

@xaelophone

Copy link
Copy Markdown
Collaborator

Summary

  • Add live password validation checklist on the signup form — shows 3 requirements (8+ chars, number, symbol) that update as the user types
  • Disable submit button until all password requirements are met
  • Return specific server-side error messages instead of generic "Invalid request" when password validation fails
  • Forward Supabase's error message on account creation failure for better debugging

Test plan

  • Visit /signup → enter invite code → start typing password → checklist appears
  • Type abc → all 3 items dim (unmet), button disabled
  • Type abcdefgh → "At least 8 characters" met, other 2 unmet, button disabled
  • Type abcdefg1! → all 3 met, button enabled
  • Submit with valid password → account created successfully
  • Build passes (npm run web:build)

🤖 Generated with Claude Code

Users got a generic "Invalid request" error when their password didn't meet
requirements. Now the signup form shows a live checklist (8+ chars, number,
symbol) that updates as the user types, and the submit button stays disabled
until all requirements are met. Server-side errors are also more specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercel Bot commented Feb 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hermes Building Building Preview, Comment Feb 24, 2026 8:28pm

Request Review

@xaelophone
xaelophone merged commit 6121e28 into main Feb 24, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant