London | 26-ITP-January | Carlos Abreu | Sprint 2 | Form Controls

[carlosyabreu]

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

Form controls project to be merge into upstream main branch

[netlify]

✅ Deploy Preview for cyf-onboarding-module ready!

Name	Link
🔨 Latest commit	8c501e5
🔍 Latest deploy log	https://app.netlify.com/projects/cyf-onboarding-module/deploys/69868036ad484c00082304ab
😎 Deploy Preview	https://deploy-preview-1155--cyf-onboarding-module.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	2 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 84 (🔴 down 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.

[A-O-Emmanuel]

I left some comments for you.

[A-O-Emmanuel]

Can you think of another way to verify if the customer name is a valid name

[carlosyabreu]

Certainly!
Here is one alternative approaches to validating a customer name in HTML form controls:

Using pattern attribute with regex
This allows for more specific validation patterns:

Name

Must be at least 2 characters long

[A-O-Emmanuel]

Yes, do that.

[A-O-Emmanuel]

Can you also think of another way to verify if the customer email is a valid email?

[carlosyabreu]

Using multiple attributes for comprehensive validation

Email Address

We'll use this to verify your email format (6-254 characters)