Preventing incorrect characters vs. showing an error state #2533
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @ceyerkes! 👋 We currently don’t have formal guidelines around this. We know our product owners are better equipped than us in handling validation for their product and customer needs. Handling validation for something like phone numbers requires more business logic, understanding our users’ needs and how different countries handle phone numbers that the Phone Numbers team would be much better equipped to handle (as Sarah Li said in a discussion not too long ago). It could be helpful for you to collaborate with the designers on that team on best practices in handling phone numbers, and seeing if their team has plans to build a shared component for this use case. I do have a few suggestions/considerations below:
Additionally, here are some related GH discussions to reference: Please let us know if you reach out to the Numbers team and possibly would like to contribute some guidance around this to Paste! |
Beta Was this translation helpful? Give feedback.
Hi @ceyerkes! 👋
We currently don’t have formal guidelines around this. We know our product owners are better equipped than us in handling validation for their product and customer needs.
Handling validation for something like phone numbers requires more business logic, understanding our users’ needs and how different countries handle phone numbers that the Phone Numbers team would be much better equipped to handle (as Sarah Li said in a discussion not too long ago). It could be helpful for you to collaborate with the designers on that team on best practices in handling phone numbers, and seeing if their team has plans to build a shared component for this use case.
I do have a few suggesti…