Skip to content

ZA | MAY-2025 | NOKWANDA PHEWA | FORM CONTROLS #646

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

NokwandaPhewa
Copy link

@NokwandaPhewa NokwandaPhewa commented May 30, 2025

Changelist

-Implemented a complete t-shirt order form with validation that meets all project requirements.

  • Enhanced name validation to prevent space-only entries
  • Standardized labeling for better consistency
  • Documented design choices for input types

Self-Checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with ZA | MAY-2025 | NOKWANDA PHEWA | FORM-CONTROLS
  • I have tested my changes (validation, Lighthouse scores)
  • My changes follow the style guide
  • My changes meet the requirements of this task

Copy link

netlify bot commented May 30, 2025

Deploy Preview for cyf-onboarding-module ready!

Name Link
🔨 Latest commit d4d6ca8
🔍 Latest deploy log https://app.netlify.com/projects/cyf-onboarding-module/deploys/683dd0f2e2f70800084de8de
😎 Deploy Preview https://deploy-preview-646--cyf-onboarding-module.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
2 paths audited
Performance: 100 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 88 (🟢 up 2 from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@NokwandaPhewa NokwandaPhewa added the Needs Review Participant to add when requesting review label May 30, 2025
Copy link
Contributor

@cjyuan cjyuan left a 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, and form implementation is solid! Great job!

Regarding your implementation

  1. Can you address my suggestions/questions which I left as inline comment with the code?

  2. The Lighthouse Accessibility score of your page is not yet 100. Can you improve the score to 100?

Regarding your PR description

  1. Can you format the checked boxes using the proper Markdown syntax so that they look something like this?
    image
    (With proper Markdown syntax, we can use mouse to check/uncheck the items)

  2. Can you also provide a brief description (under the "Changelist" section) summarizing the purpose of the PR and the changes you’ve made?

The code for the "Changelist" section looks like this in the PR template:

### Changelist

Briefly explained your PR.

Comment on lines 43 to 59
<input type="radio" id="xs" name="size" value="XS" required>
<label for="xs">XS</label><br>

<input type="radio" id="s" name="size" value="S">
<label for="s">S</label><br>

<input type="radio" id="m" name="size" value="M">
<label for="m">M</label><br>

<input type="radio" id="l" name="size" value="L">
<label for="l">L</label><br>

<input type="radio" id="xl" name="size" value="XL">
<label for="xl">XL</label><br>

<input type="radio" id="xxl" name="size" value="XXL">
<label for="xxl">XXL</label><br><br>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Between using radio buttons and using a drop-down list, which of them is more suitable for reading one of six sizes?

@cjyuan cjyuan added Reviewed Volunteer to add when completing a review and removed Needs Review Participant to add when requesting review labels Jun 2, 2025
@NokwandaPhewa
Copy link
Author

NokwandaPhewa commented Jun 2, 2025

Thank you for your review @cjyuan , i have made improvements and also updated the PR description with proper markdown checkboxes. Could you kindly review again and let me know if i need to make further adjustments.Thanks

Copy link
Contributor

@cjyuan cjyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes you made are quite good.

  1. The Lighthouse Accessibility score is not yet 100. Can you improve the score to 100?

  2. We can reply directly to an inline comment to keep all related discussions organized in one place. Can you address this inline comment in my previous comment?
    image

  3. Don't forget to replace the label from "Reviewed" to "Needs review" if your changes is ready to be reviewed.

Comment on lines +29 to +30
minlength="2" pattern=".*[^ ].*"
title="Please enter at least 2 non-space characters"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description given in the title attribute does not quite match what the pattern check.
Current pattern can guarantee only "at least one non-space character" in the name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reviewed Volunteer to add when completing a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants