Repository navigation
[Phone field] - extend the phoneFormat field or create a new one to return format properties along with the selected format #441
Description
What problem does this address?
Phone field currently returns two formats: international and standard. By having this value, you don't get much except its name. It would be nice to expand that field or create another one to get the currently selected phone format with their values:
'standard' => array(
'label' => '(###) ###-####',
'mask' => '(999) 999-9999',
'regex' => '/^\D?(\d{3})\D?\D?(\d{3})\D?(\d{4})$/',
'instruction' => '(###) ###-####',
'type' => 'standard',
),
So we know its properties, which would help in implementing it. In the same way, we could support more custom formats added with thegform_phone_formats filter
What is your proposed solution?
Create a new field for the Phone field which will be returning other props, like label, mask, regex and instruction along with selected type. Make sure, custom formats will be supported as well
What alternatives have you considered?
No response
Additional Context
No response
Activity
justlevine commentedon Aug 2, 2024
Thanks for suggesting this @Gytjarek !
Normally, I'm not a fan of mixing implementation details with implementation definitions, but in this case, since
gform_phone_formatsexposes the entire object, we want to be able to provide the site-specific context.Feel free to submit a PR if you want this in sooner than I can get around to it.
feat: Add phoneFormatProperties field to resolve issue AxeWP#441
feat: Add phone format properties to resolve issue #441 (#475)
justlevine commentedon Feb 14, 2026
This was added in #475 via the
PhoneFormat._phoneFormatExperimental: GfPhoneFormatfield. In the next breaking release, thephoneFormatfield will be updated to use the new type.Leaving this PR open until then.
justlevine commentedon Jul 11, 2026
🤖 Automated Triage
Classification: type: enhancement ⚡ · priority: medium · breaking change 💥
Agent-feasible: Yes — bounded scope (extend Phone field type with format properties), though already marked in progress.
Estimated effort: Agent medium · Human medium
Summary: Request to expose phone format properties (label, mask, regex, instruction) via a new GraphQL field, including support for custom formats registered through the
gform_phone_formatsfilter. The breaking change label suggests the new field may alter the existingphoneFormatreturn shape. Already in progress — agent should verify whether active work exists before intervening.Next steps: Already in progress. If the active PR has stalled, agent can pick up implementation. Ensure custom formats from
gform_phone_formatsare included in the resolver, not just the two built-in formats.