dev/core#2806 Fix accidental exposure of v4 tokens #21337
Merged
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#2806 Fix accidental exposure of v4 tokens
Before
In master (only) tokens were being displayed like '
{contribution.Partner.name'}
referring to custom fields. Long term we want this more portable format but we are not ready to define it yetAfter
Extraneous tokens removed
Technical Details
@demeritcowboy I haven't added a test here because I'm working on tests for this stuff in
CRM_Utils_TokenConsistencyTest
but I already have an open test against this class - https://github.com/civicrm/civicrm-core/pull/21327/files - unfortunately that one didn't pick it up because contribution recur doesn't 'normally' have custom data - but I do intend to add more tests for this stuff in that class . The class I did the original contribution tokens test in unfortunately uses rollback which doesn't play nice with custom fields so I 'moved'Comments