Current dbal storage does not support extensions.

[wizhippo]

Perhaps the serialization format for dbal should be changed to RFC-3966?

Discussion at misd-service-development#183

[odolbeau]

Hi @wizhippo
I took a look at the discussion you mentioned & I think we should create another Doctrine Type (or find a way to configure the actual one) instead of changing the current Doctrine Type default behavior.
WDYT?

[wizhippo]

I would be fine either way. Lets make sure we document it so no one is surprised all their extensions are missing. I would prefer though that by default extensions are stored. I know this is a BC break but I believe it would the the default expected behavior to support extensions as the phonenumber type supports methods specifically for has/get/set for the extension.

[Nek-]

Hello @wizhippo thanks for reaching out on the topic.

For this, to work I actually suggest creating an embeddable object. As a European, I have no idea what is a phone extension. But not supporting it in the standard format number comes from google.

The doctrine type we suggest cannot as it supports in any way the extension system. But is there any format supported by the library that actually does? Can you provide examples?

As I understand we should actually store the phone number in RFC3966 format instead of E164, is that correct? In this case, the solution looks simple: we need to change the phone number type by making a new one.