Skip to content

Glasgow | May-2026 | Craig Stoddart | Sprint 1 | Form Controls #1413

Open
CraigStodd wants to merge 17 commits into
CodeYourFuture:mainfrom
CraigStodd:feature/form-control
Open

Glasgow | May-2026 | Craig Stoddart | Sprint 1 | Form Controls #1413
CraigStodd wants to merge 17 commits into
CodeYourFuture:mainfrom
CraigStodd:feature/form-control

Conversation

@CraigStodd
Copy link
Copy Markdown

@CraigStodd CraigStodd commented Jun 4, 2026

LINK TO PREVIOUS PR:

Learners, PR Template

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

Updated to include changes suggested in previous pull request.
Implemented changes that meet all requirements for the Form Control exercise

@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 4, 2026

Deploy Preview for cyf-onboarding-module ready!

Name Link
🔨 Latest commit 537aeb3
🔍 Latest deploy log https://app.netlify.com/projects/cyf-onboarding-module/deploys/6a217266ab8d4b0008ff0e27
😎 Deploy Preview https://deploy-preview-1413--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: 86 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

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

@CraigStodd CraigStodd added the Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. label Jun 4, 2026
@CraigStodd
Copy link
Copy Markdown
Author

Hi @cjyuan, here is the updated PR with the changes you suggested.

Copy link
Copy Markdown
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.

Changes look good.

I only a few more minor requests.

Comment thread Form-Controls/index.html
Comment on lines +69 to +72
<label
>XS:
<input type="radio" name="Size" value="XS" required />
</label>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you look up "Should the text associated with a radio button be placed on left or right of the radio button?"

Change is optional.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Sure, I'll look into it.

Comment thread Form-Controls/index.html
</div>
</div>

<br />
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Consider using CSS to control spacing between elements instead of using <br> tags. This approach is generally more maintainable and semantically correct.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Ok.

Comment thread Form-Controls/index.html

<label
>S:
<input type="radio" name="Size" value="S" required />
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The convention is to use lowercase kebab-case values for the name attribute (and also for id and class attributes)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Noted, I'll change this.

@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 Jun 4, 2026
@CraigStodd
Copy link
Copy Markdown
Author

Hi @cjyuan, I've implemented the changes you suggested. Let me know if there are any further issues. Thanks.

@cjyuan
Copy link
Copy Markdown
Contributor

cjyuan commented Jun 5, 2026

  • I don't see any new commits on this branch.

    • Check if you have pushed the commits made on your computer to GitHub.
    • Check if you have made the commits on the right branch.
  • When this PR is ready to be re-reviewed, add a "Needs review" label to this PR.

@CraigStodd
Copy link
Copy Markdown
Author

They appear to have gone to this repository: https://github.com/CraigStodd/Module-Onboarding/tree/Glasgow-May-2026-Craig-Stoddart-Sprint-1-Form-Control.

I'm not sure how to fix this. I think renaming the branches has complicated things.

@cjyuan
Copy link
Copy Markdown
Contributor

cjyuan commented Jun 5, 2026

It seems that branch is not related to any opened PR, so I don't think changing it will affect your current PRs.

The easiest way to transfer your changes to this branch is

  1. Switch to this branch. On VS Code, the "current branch name" is usually located at the lower left corner of the VS Code window.
  2. Update the two files on this branch (copying your code from the "Glasgow...-Form-Control" branch is one option).
  3. Commit the change and push the commit to GitHub.

Note: I think what happened was that you renamed the "Glasgow ..." branch on GitHub, but not on your computer, and you continued working on your original "Glasgow ..." branch on your computer. When you pushed the original branch to GitHub, the "Glasgow ..." branch was recreated on GitHub".

If the feature/form-control branch does not exist on your computer, you can fetch it from GitHub.

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 with trainee action still to take.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants