dev/core#2817 towards deprecating legacy replaceCaseTokens
#21380
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
dev/core#2817 towards deprecating legacy
This adds support for the syntax
{case.status_id:label} which what we agreed as a preferred syntax
to disambiguate the demands for labels vs ids vs machine names in
various implementations.
The new (preferred) label is advertised - but the old
one still works
Before
{case.status_id}
renders (e.g.) 'Ongoing'{case.case_type_id}
renders (e.g 'Housing Support')After
The unambiguous versions work & are supported. The ambiguous ones also still work - but in the token processor variant they will render the DB value
{case.status_id}
renders (e.g.) 'Ongoing'{case.status_id:label}
renders (e.g.) 'Ongoing'{case.case_type_id}
renders (e.g 'Housing Support'){case.case_type_id:label}
renders (e.g 'Housing Support')Technical Details
See https://lab.civicrm.org/dev/core/-/issues/2817 for next steps
Comments