#vebt-815 #comment Changed phone schema pattern in 22-10282

[govcioChad]

Are you removing, renaming or moving a folder in this PR?

• [x] No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• [ ] Yes, I'm removing, renaming or moving a folder

Summary

- (Summarize the changes that have been made to the platform)

• Updated the phone schema in 22-10282 form to allow dashes

  - (If bug, how to reproduce)

• Phone number wasn't allowing dashes and created an error if dashes were present

  - (What is the solution, why is this the solution)

• Switched to the web component pattern phoneUI definition

  - (Which team do you work for, does your team own the maintenance of this component?)

• GovCIO, we are the code owners

  - (If using a flipper, what is the end date of the flipper being required/success criteria being targeted) N/A

Related issue(s)

Jira -> https://jira.devops.va.gov/browse/VEBT-815

Issue -> On the STEP 1: Your personal information of the 22-10282 form, if you enter a phone number with dashes (xxx-xxx-xxxx) & brackets for area code ((444)-444-4444) you get the validation warning "Please enter a 10-digit phone number (with or without dashes)" that blocks continuation of the form.

Fix -> Remove the validation when a user enters a phone number that includes dashes. Please see image below.

Testing done

- Describe what the old behavior was prior to the change

• Dashes in phone number field were not acceptable

  - Describe the steps required to verify your changes are working as expected

• Dashes in phone number field are now acceptable
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

Before:

After:

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

Quality Assurance & Testing

• [x] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [x] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• [x] Linting warnings have been addressed
• [ ] Documentation has been updated (link to documentation *if necessary)
• [ ] Screenshot of the developed feature is added
• [ ] Accessibility testing has been performed

Error Handling

• [ ] Browser console contains no warnings or errors.
• [ ] Events are being sent to the appropriate logging solution
• [ ] Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• [ ] Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?