I have several forms where I want to save the phone numbers of users. In the actual database the field is a string and I would like to save in +160277688 format where 1 is country code, then area code then the number.
When I think about user inputs and enforce via my change set and form itself, I am debating how much logic goes into the change set versus closer to the form itself. Has anyone tackled phone numbers and wanted to save in a particular format?
Thank showing the different paths is really helpful. I am using Twilio for a side project and so its not just real people, its matching up a phone number to phone number automatically, etc. It seems like libphonenumber would be the way to go (I see an elixir port of it).
It seems like Phoenix.HTML.Form works pretty tightly with the changeset by default. Is it usually best to put the validation and converting to a E.164 proper format for then storing in the database all in the ecto changeset, while leaving the form to be just a single string input?
I’m using Twilio as well, so I store the number in the DB in Twilio-compatible format. For the presentation I use Cleave.js and do the conversion in the controller since I treat the formatting as the UI concern.
Thank you thats good to hear. Right now I have it taking a country code and national number from the form and having a changeset function that validates and puts the final e164 format number as the phone number which is stored.
Cleave.js looks great, I will definitely look into using!