Skip to content

Comments

Birmingham | 26-ITP-Jan | Mohammed Omer | Sprint 2 | Form-Control#1184

Open
mo-omer wants to merge 6 commits intoCodeYourFuture:mainfrom
mo-omer:Form-Control
Open

Birmingham | 26-ITP-Jan | Mohammed Omer | Sprint 2 | Form-Control#1184
mo-omer wants to merge 6 commits intoCodeYourFuture:mainfrom
mo-omer:Form-Control

Conversation

@mo-omer
Copy link

@mo-omer mo-omer commented Feb 19, 2026

Self checklist

  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • My changes meet the requirements of the task
  • I have tested my changes
  • My changes follow the style guide

Changelist

included semantic wrappers for better grouping form controls and simpler code.

@netlify
Copy link

netlify bot commented Feb 19, 2026

Deploy Preview for cyf-onboarding-module ready!

Name Link
🔨 Latest commit 0457884
🔍 Latest deploy log https://app.netlify.com/projects/cyf-onboarding-module/deploys/699b4bfb71126000086bc13d
😎 Deploy Preview https://deploy-preview-1184--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: 91 (🟢 up 5 from production)
PWA: -
View the detailed breakdown and full score reports

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

@mo-omer mo-omer added the Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. label Feb 19, 2026
@hkavalikas hkavalikas added Review in progress This review is currently being reviewed. This label will be replaced by "Reviewed" soon. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Feb 19, 2026
@hkavalikas hkavalikas self-requested a review February 19, 2026 06:52
</main>

<footer>
<p>Website Dedicated To T-shirt Sale</p>

Choose a reason for hiding this comment

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

We had slightly different requirements for the content of this footer. Let's check the edited files again and address it.

</p>
</section>

<!-- Colour Selection -->

Choose a reason for hiding this comment

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

Let's look into the colour selection a bit more, specifically the options. Do you see anything that might look off and not fulfil the requirements?

Red
</label>

<p>

Choose a reason for hiding this comment

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

We are wrapping radio buttons into paragraphs, which might be a better fit for text. Can you find a more appropriate tag to wrap them instead?

</div>

<label>
<input type="radio" name="colour" value="red" required />

Choose a reason for hiding this comment

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

This radio button was declared in a slightly different way than others, it's not getting the CSS changes and doesn't fulfil the original requirements to be associated with the input. How can we improve it?

@hkavalikas hkavalikas added Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Review in progress This review is currently being reviewed. This label will be replaced by "Reviewed" soon. labels Feb 19, 2026
@hkavalikas
Copy link

Let's also improve the Changelist by listing what work has been done, generally speaking we should give a high-level summary of the changes over mentioning things like "simpler", "better" or "cleaner" code to help the reviewer get an idea of what they are about to review as well as serve as a sort of documentation if someone has to refer back to it in the future so they don't need to go through all files again to get an understanding of what has been changed.

@mo-omer mo-omer added Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. and removed Reviewed Volunteer to add when completing a review with trainee action still to take. labels Feb 21, 2026
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.

Comment on lines 155 to 164
<div>
<input type="radio" id="red" name="colour" value="red" required />
<label for="red">Red</label>
</div>


<div>
<input type="radio" id="black" name="colour" value="black" required />
<label for="black">Black</label>
</div>
Copy link
Contributor

@cjyuan cjyuan Feb 22, 2026

Choose a reason for hiding this comment

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

This implementation does not quite meet the requirements specified in README.md. Please check the spec to find out what you missed.

Copy link
Author

Choose a reason for hiding this comment

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

added 3rd colour section to meet README requirement

       <div>
          <input type="radio" id="blue" name="colour" value="blue" required />
          <label for="blue">Blue</label>
        </div>

Comment on lines 177 to 178
<input type="radio" id="xs" name="size" value="XS" required />
<label for="xs">XS</label>
Copy link
Contributor

Choose a reason for hiding this comment

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

Could also consider wrapping the radio button input inside the label tag as:

              <labe>
              <input type="radio" name="size" value="XS" required />
              XS
              </label>

This way, you don't need to use the for and id attribute.

Also, among the radio buttons in the same button group, we don't need multiple required -- one is enough.

Copy link
Author

Choose a reason for hiding this comment

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

wrapped radio button input inside label tag and removed redundant required, id and for attributes since label wrap inputs

          <label>
            <input type="radio" name="size" value="XS" required /> XS
          </label>

@cjyuan cjyuan added Complete Volunteer to add when work is complete and all review comments have been addressed. Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. Complete Volunteer to add when work is complete and all review comments have been addressed. labels Feb 22, 2026
@cjyuan
Copy link
Contributor

cjyuan commented Feb 22, 2026

@mo-omer
Please note that in CYF courses, the recommended way to inform the reviewer of your changes is to do both of the following:

  • Reply to their feedback.
    • In the responses, clarify how each piece of feedback was addressed to demonstrate that you've carefully reviewed the suggestions.
      • You may find the suggestions in this PR Guide useful.
    • Your response may trigger a notification (depending on the reviewer's settings), helping ensure they’re aware of the updates you’ve made.
  • Replace the "Reviewed" label by a "Needs review" label (which you have done -- great!)
    • Without this label, the reviewer would not know if your changes is ready to be reviewed.

@mo-omer mo-omer added Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. and removed Reviewed Volunteer to add when completing a review with trainee action still to take. labels Feb 22, 2026
@cjyuan
Copy link
Contributor

cjyuan commented Feb 22, 2026

  • According to https://validator.w3.org/, there is one warning. Can you address it? (I don't think the Submit button needs its own "section")

  • Why markup the radio buttons for colours and sizes in different syntax?

<input type="radio" id="blue" name="colour" value="blue" required />
<label for="blue">Blue</label>
<label>
  <input type="radio" name="size" value="M" /> M
</label>

@cjyuan cjyuan added Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Feb 22, 2026
@mo-omer mo-omer added Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. and removed Reviewed Volunteer to add when completing a review with trainee action still to take. labels Feb 22, 2026
@mo-omer
Copy link
Author

mo-omer commented Feb 22, 2026

  • According to https://validator.w3.org/, there is one warning. Can you address it? (I don't think the Submit button needs its own "section")
  • Why markup the radio buttons for colours and sizes in different syntax?
<input type="radio" id="blue" name="colour" value="blue" required />
<label for="blue">Blue</label>
<label>
  <input type="radio" name="size" value="M" /> M
</label>

changed syntax on radio button to match the rest
removed section tag from submit button

@cjyuan
Copy link
Contributor

cjyuan commented Feb 22, 2026

Changes look good. Well done.

@cjyuan cjyuan added Complete Volunteer to add when work is complete and all review comments have been addressed. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Feb 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complete Volunteer to add when work is complete and all review comments have been addressed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants