(Mostly a question for @fabpot and @webmozart.)

If there were a phone number field type and/or validation constraint in Symfony core (which is a common requirement, but is far from trivial to do well), what should it do exactly?

I see the options as:

Just have a normal HTML tel field that deals with strings (ie it won't check that it is actually a phone number). Simple and doesn't require anything external (in the same way to the money type doesn't use a proper money library).
Same as 1 except that it uses libphonenumber to check that the string is a phone number ([WIP][Form] Add TelType #11360 appears to be trying to do this, but it's a bit broken). This would allow a constraint.
Move what's in my bundle to core (ie a field type that takes/outputs libphonenumber\PhoneNumber objects and the constraint).
Don't include it in core and instead document how to use types provided by external bundles even if the form component is used standalone (if this starts to happen I think the money type should follow suit).

I don't think 1 or 2 are that useful (as phone numbers don't work as strings very well, in the same was money doesn't). I'm happy for 3 or 4 to happen, the bundle does a few other things so would exist either way (if 3 did happen, I would deprecate the bundle's types, but continue to provide them for earlier Symfony versions - assuming the implementation is compatible).

Uh oh!

[Form] missing tel field type #8026

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions