APIv4 ConformanceTest - Demonstrate entity APIs which fail to emit hook_civicrm_post(delete)
#22205
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
Add assertions to APIv4's
ConformanceTest
to determine whetherFooEntity::delete()
emitshook_civicrm_post('delete', 'FooEntity')
.ping @colemanw
Before
Some entities emit
hook_civicrm_post('delete'...)
, and some don't... and it's hard to be sure which is which.After
Some entities emit
hook_civicrm_post('delete'...)
, and some don't... and the test tells us which is which.Comments
As discussed in #22199 (comment), the event
hook_civicrm_post('delete'...)
becomes more important in the currentmaster
-- if this event is not supported, then the managed-entities cannot be cleaned up.The list of non-conformant entities is fairly long:
CaseType
,Contact
,ContactType
,FinancialAccount
,FinancialType
,LocationType
,MembershipStatus
,MembershipType
,MessageTemplate
,OptionGroup
,PaymentProcessor
,PaymentProcessorType
,RelationshipType
,WordReplacement
.(Note:
Contact
is probably OK, but it fails the test because it uses alternative names likeIndividual
.)