-
-
Notifications
You must be signed in to change notification settings - Fork 266
Sheffield | 3 May-2025 | Xiayidan Abuduxukuer | Form Controls #705
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
base: main
Are you sure you want to change the base?
Sheffield | 3 May-2025 | Xiayidan Abuduxukuer | Form Controls #705
Conversation
✅ Deploy Preview for cyf-onboarding-module ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Code is error-free and well-indented. Form implementation is solid and PR description is nicely prepared. Excellent!
A PR branch should include only the changes relevant to the specific task or feature it addresses. This branch, created for the "Form-Controls" exercise, currently contains some unrelated changes (see pic)
Note: I assume these four files are not part of your form implementation.
Can you carry out the following steps to make this branch clean?
- In
form-controls-completed
branch, delete the sub-folderwireframe-task
. - In
form-controls-completed
branch, replace bothindex.html
andstyle.css
in the "Wireframe" folder by the version of the files in themain
branch. You can download them from here:
https://github.com/Shayida999/Module-Onboarding/tree/main/Wireframe - Commit the change (there should be 4 affected files)
- Push your commit to Github.
Form-Controls/index.html
Outdated
<input | ||
type="Text" | ||
id="CustomerName" | ||
name="CustomerName" | ||
required | ||
minlength="2" | ||
aria-describedby="NameHelp" | ||
/> |
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.
Currently a user can enter a name consisting of only space characters (e.g., " "). Can you enforce a stricter validation rule using the pattern
attribute to disallow any name that contains only space characters?
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.
Hi CJ.
I have now:
Removed the wireframe-task folder
Restored the correct Wireframe files from main
Added a pattern to the name input to block whitespace-only names
Is everything ok now?? Thank you
Changes look good! Well done! |
I’m really glad everything looks good now — thank you so much! I just wanted to let you know: while I was checking your feedback, my baby accidentally pressed some keys on my laptop 😅 and I think something may have been deleted in the “Labels” section on GitHub. So sorry about that TvT. and i have one more question ,just to confirm, is the final step now to complete the Duolingo test? Should I aim to finish it today? |
I responded your question about Duolingo test on Slack. |
Learners, PR Template
Self checklist,
Changelist
Questions
None at the moment — ready for review!