Bug Description:
There is a bug in the user signup validation logic. Even when the user enters a password that meets the criteria (e.g., more than 7 characters) and both the password fields match, the form displays a false validation error banner: "Password must be at least 7 characters long." and prevents submission.
Steps to Reproduce:
- Go to the PiperChat registration page.
- Fill in a valid email and username.
- Enter a password that is clearly longer than 7 characters (e.g., 14 characters long).
- Re-enter the same password in the confirmation field.
- Notice that the error banner appears and blocks the registration process.
Screenshots / Visual Proof:
Expected Behaviour:
The form should validate the length correctly. If the input string length is >= 7, the error banner should disappear, and the user should be allowed to proceed by clicking "Continue".
Possible Root Cause:
- The validation trigger might be lagging behind the state updates (
onChange).
- The character length condition check logic in the backend/frontend controller might be incorrectly configured or looking at a wrong input field value.
I am a contributor participating in GSSoC '26. I would love to look into the authentication component files and resolve this validation logic error. Please assign this issue to me!
Bug Description:
There is a bug in the user signup validation logic. Even when the user enters a password that meets the criteria (e.g., more than 7 characters) and both the password fields match, the form displays a false validation error banner:
"Password must be at least 7 characters long."and prevents submission.Steps to Reproduce:
Screenshots / Visual Proof:
Expected Behaviour:
The form should validate the length correctly. If the input string length is
>= 7, the error banner should disappear, and the user should be allowed to proceed by clicking "Continue".Possible Root Cause:
onChange).I am a contributor participating in GSSoC '26. I would love to look into the authentication component files and resolve this validation logic error. Please assign this issue to me!