-
Notifications
You must be signed in to change notification settings - Fork 369
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
🛠️ Fix: Name Field validation in Feedback page #2330
Conversation
@akash70629 is attempting to deploy a commit to the Vivek Prajapati's projects Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe changes in the Changes
Assessment against linked issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
src/User/components/FeedbackForm/Feedback.jsx (2)
171-177
: Improve name validation and error handlingThe changes successfully implement the required validation for the name field, addressing the issue mentioned in #2329. However, there are a few points to consider for improvement:
- The error message could be more specific about allowing spaces.
- The current pattern doesn't account for names with hyphens or apostrophes, which are common in some names.
- The implementation doesn't handle the case where a user pastes invalid content into the field.
Consider the following improvements:
- Update the error message to be more specific:
e.target.setCustomValidity('Please enter a valid name using only letters and spaces.');
- Modify the pattern to allow for hyphens and apostrophes:
pattern="[a-zA-Z' -]+"
- Add an onChange handler to validate pasted content:
onChange={(e) => { handleNameChange(e); e.target.checkValidity(); }}These changes will make the validation more robust and user-friendly while still meeting the requirements of the PR.
171-177
: Consider applying similar validation to other fieldsWhile the changes successfully implement validation for the name field, it's worth considering if similar validation should be applied to other fields in the form, such as the email field. This would ensure consistency in form validation and improve overall data quality.
Consider implementing custom validation for the email field as well. For example:
<input type="email" id="email" value={email} onChange={handleEmailChange} placeholder="Enter your email" required pattern="[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}" onInvalid={(e) => { e.target.setCustomValidity('Please enter a valid email address.'); }} onInput={(e) => { e.target.setCustomValidity(''); }} />This would provide a more robust validation for the email field, enhancing the overall form validation strategy.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- src/User/components/FeedbackForm/Feedback.jsx (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
src/User/components/FeedbackForm/Feedback.jsx (1)
171-177
: Confirmation: PR objectives and linked issue addressedThe implemented changes successfully address the PR objectives and resolve the issue described in #2329. The name field now restricts input to alphabetical characters and spaces, preventing the submission of symbols and special characters.
This implementation effectively enhances the validation of the "Name" field as requested, improving the overall quality of submissions and reducing the potential for spam or invalid entries.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Congratulations, Your pull request has been successfully merged 🥳🎉 Thank you for your contribution to the project 🚀 Keep Contributing!! ✨ |
Changes proposed
The "Name" field on the Feedback page only accepts alphabetical letters (a-z, A-Z). Currently, the field does not allow users to input symbols and special characters, which may lead to invalid or spam submissions.
Fixes Issue
Closes #2329
Screenshots
Before
After
Checklist
Summary by CodeRabbit