department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
99 stars 69 forks source link

UX: Drupal treatment for handling international phone numbers and verify which fields need it #18959

Open davidmpickett opened 3 months ago

davidmpickett commented 3 months ago

Statuses

[2024-11-07] [Jill] DST has resolved DST #3222 which will ship in next DS version [2024-09-20] [Fran] DST ticked is in their review/prioritize pipeline. Keeping this one open and blocked. [2024-09-10] [Fran] Amanda has confirmed that DST component variant for international phone numbers - in progress. We may be able to close this ticket after their work is completed. Leaving in draft and adding Blocked tag.

Description

The phone number field in Drupal has built-in validation. That validation does not allow use of international country codes. Assuming that phone number standardization work has shipped / been enabled, in the world of the phone number paragraph legacy widget: We need to:

Fields where the change needs to be applied

Which fields need to support international numbers? Presumably all of them, on behalf of Manila.

Acceptance criteria

aklausmeier commented 3 months ago

DST component variant for international phone numbers - in progress cc @davidmpickett

davidmpickett commented 3 weeks ago

Because of the modular nature of Drupal, this is an instance where it doesn't necessarily make sense to lead with the UX. Our ability to customize the UX will greatly depending on the technical implementation used for international phone numbers.

For instance International Phone provides an all-in-one field for international phone numbers. it comes with it's own widget settings and possibly will have built in error messages that can't easily be modified.

Phone Number (field) has a slightly different look

Or we could create our own country code field and using the existing field_phone_number text field for the other ten digits.