APIv4 export action: find DAO by ID instead of just calling the constructor and setting the ID #24089
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
Find DAO by ID instead of just calling the constructor and setting the ID. Otherwise, finding references might fail because of missing entity values when comparing, e.g.
option_group_id
for OptionVaue BAOs.Before
Running e.g.
OptionGroup.export
might not work when finding references to option values, because comparingoption_group_id
will evaluate tonull == null
here:civicrm-core/CRM/Core/Reference/OptionValue.php
Lines 43 to 45 in c75c0f2
After
Comparison with BAO properties will be correct with the BAO being loaded via
\CRM_Core_DAO::findById()
instead of just calling the constructor and setting the BAO ID.Technical Details
I'm not sure what might cause that
null == null
comparison in the first place, in my case it was comparing two unrelated option values that had bothoption_group_id
not set.