-
Notifications
You must be signed in to change notification settings - Fork 127
🚀 Feature: Password field validation before submission and show/hide password feature #50
Comments
I would like to work on this feature. Kindly assign it to me! |
Kindly assign this issue to me |
Hello! I would love to work on this issue. Kindly assign it to me |
I would like to work. |
I would like to work on this feature. |
i can do it! please assign |
Hi, I'm interested in contributing to this issue. I have experience with form validation and user experience design, and I believe I can make a valuable contribution. Here are some ideas I have for implementing this feature: For password field validation, we could use a regular expression to check that the password meets the minimum requirements (e.g., length, complexity). We could also display a helpful error message to the user if the password is invalid. For the show/hide password feature, we could use a small eye icon next to the password field. When the user clicks on the icon, the password field would be toggled between plain text and hidden. I'm also happy to discuss other ideas or suggestions you have. Sincerely, |
Hey, I would love to try this out. Can it still be assigned to me? |
🔖 Feature description
Password field validation - Right now the user is unable to figure out the reason for signup failure. I also had to check the network tab to figure all out. Having validation before sending request will reduce unnecessary requests to backend and provide a better user experience.
Show/Hide password - Adding a show/hide feature for password field will improve the UX.
🎤 Pitch
Users need to know the requirements for each field in a form. For this purpose, form validation is essential. Also it will improve the user experience and reduce unnecessary failed requests.
Also one would like to see what password they have entered. Giving the flexibility to switch between show/hide password is essential.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: