(REF) dev/core#1744 - Simplify Afform event naming #20555
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
This PR replaces the last usage of constants for event names in CiviCRM code base with string literal.
Before
The
ext/afform/core/afform.php
file uses constants for event names.After
The
ext/afform/core/afform.php
file uses string literal for event names.Technical Details
Since CiviCRM 5.26, the convention was to use string literal for event names and the usage of constants was deprecated according to this issue dev/core#1744. This was the last usage of constants for event names in CiviCRM code base.
Comment
Also, it addresses the failing deployments for two of our sites with
afform
extension enabled after deploying them on another server e.g. creating dev/staging sites.I've seen the following error on two sites that had
afform
extension enabled recently: