API4 naming for custom field tokens (:name / :label)
Overview
With all the work on standardization of token processing we have come a long way. One missing element I think is the availability of api4 naming of the custom field tokens. In #2650 (closed) this is out of scope. I would like to get this on the radar. Maybe it is an easy improvement.
Current behaviour
For core tokens :label and :name are supported to provide the raw value of label of the field. (eg. {contact.communication_style_id:name} / | {contact.communication_style_id:label}
)
For custom fields this is not available:
{contact.custom_1173:name} / {contact.custom_1173:name}
The label of the field/token could be: "This is a long label" and the value: "long")
Proposed behaviour
For consistency and for easy usage in smarty conditionals it would be great if api4 naming availability for custom field tokens would be supported.
Comments
I can help test and sometimes I can code something myself if it an easy needle and I know where to look in the haystack The overall token issue can be found here : #2864 (closed)