Fix APIv3 profile.getfields to return correctly keyed phone field #19321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This fixes the phone profile field to have the correct field key to match profile forms.
Fixes civicrm/org.civicrm.contactlayout#91
Before
Key returned by api does not match form key for the phone field.
After
Matches and ContactLayout is able to function correctly.
Technical Details
The field key is supposed to be
phone-[location_type_id|'Primary']-[phone_type_id]
.