dev/core#2019 - Changing a case custom field from blank to something doesn't show properly what changed #19735
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
https://lab.civicrm.org/dev/core/-/issues/2019
Before
Incorrect record of what changed.
After
Correct.
Technical Details
api customvalue.getdisplayvalue does an empty() check on the passed in value and then considers that to mean it should use the existing field value in the database instead, but it's already been updated and so contains the new value, so this then incorrectly treats
''
and0
which are legitimate prior values.This api function doesn't appear to be used anywhere in universe, and was added in 5.19 for this function, so changing it is unlikely to affect anyone.
Comments
Has test.
This also includes a belated test for #19692 since the only thing extra needed to test that is to also run this test here in another locale, which it does.