Skip to content

Enhance signup UX by adding password length and match validation with…#202

Open
Heet27 wants to merge 2 commits into
mainfrom
feature/signup-password-validation
Open

Enhance signup UX by adding password length and match validation with…#202
Heet27 wants to merge 2 commits into
mainfrom
feature/signup-password-validation

Conversation

@Heet27
Copy link
Copy Markdown
Collaborator

@Heet27 Heet27 commented May 2, 2026

In this update, I focused on improving the signup form from a user experience perspective.

Previously, the form allowed users to submit passwords that were too short or did not match, which could lead to unnecessary backend errors. To fix this, I added simple client-side validation before submission.

I implemented:

  • A minimum password length check (at least 8 characters)
  • A check to ensure password and confirm password match
  • Clear error messages to guide the user when input is invalid

I made sure not to change the existing UI layout or backend logic, so the changes are safe and only improve frontend behaviour.

This helps prevent invalid requests and gives immediate feedback to users, making the signup process smoother.
22

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 47a563c7dd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

}

setError("Unsupported provider.");
onSubmit(formData);
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Include terms consent in submitted signup payload

handleSubmit now forwards formData directly, so the agreeTerms flag is never included in the payload even after consent is validated. SignUpPage/onSignUp is typed to receive SignUpSubmitPayload with agreeTerms, so this silently breaks that contract and can lead to downstream logic receiving incomplete consent data.

Useful? React with 👍 / 👎.

Comment on lines +84 to +88
<input
placeholder="Email"
value={formData.email}
onChange={(e) => onFormChange("email", e.target.value)}
className="w-full p-3 rounded-xl bg-[#173454] text-white"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore native email validation on signup form

The email input no longer declares type="email" or required, so the browser stops enforcing basic email presence/format before submit. This allows malformed or empty email values to pass client-side and fail later in submission handling, which is a regression from the previous behavior that blocked these invalid requests immediately.

Useful? React with 👍 / 👎.

@liyunze-coding
Copy link
Copy Markdown
Collaborator

@Heet27 please resolve merge conflicts

@Heet27
Copy link
Copy Markdown
Collaborator Author

Heet27 commented May 4, 2026

@Heet27 please resolve merge conflicts

Hi, I’ve resolved the merge conflicts in SignupFormPanel.tsx by aligning the file with the latest main branch UI and integrating my password validation changes (minimum length + match check). I also removed all conflict markers and ensured the component uses the correct props and handlers. The file is now clean, builds successfully, and is ready for review.

Copy link
Copy Markdown
Collaborator

@liyunze-coding liyunze-coding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

2 participants