-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#15 Requirement of Proper Input Handling in Login/Register form #29
Conversation
…ng no special symobols
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, @pand-coder! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines
@pand-coder please update the branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved!
🎉 Your pull request has been successfully merged! 🎉 Thank you for your contribution to our project. Your efforts are greatly appreciated. Keep up the fantastic work! 🚀 |
Description
Added a small warning using html and css whenver user enter a password and cursor points on password input box
validated the backend form validation used special character regex expression to prevent symbols that lead to client side injection attacks such as xss and other attacks.
Related Issues
None
Type of PR
Screenshots / videos (if applicable)
Wrote this Exception handling to ensure proper validation
Checklist
main
branch before making this PRAdditional context:
Atfirst, Tried using the alert method but it was conflicting the google app authenticator then switched to this method of warning based change with change in the signup form validation code