[REF][PHP8.2] Declare properties directly on CRM_Core_Form_EntityFormTrait #25926
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
Declare properties directly on
CRM_Core_Form_EntityFormTrait
, rather than (inconsistently) on the classes which use it.Before
The
entityFields
property was declared individually on many classes which useCRM_Core_Form_EntityFormTrait
, but not all of them. Additionally the largedocblock
was repeated many times, increasing the chance of inconsistent documentation occuring in future.The
metadata
property was always being written to as a dynamic property, causing tests to fail on PHP 8.2.After
The
entityFields
andmetadata
properties are explicitely declared on theCRM_Core_Form_EntityFormTrait
.Comments
I think there may be a small backwards compatiability risk here, if third-party extensions are using
CRM_Core_Form_EntityFormTrait
, but have declaredentityFields
ormetadata
aspublic
properties (although I've not actually tested what would happen in this scenario)There is still a
_BAOName
property to tackle, which I'll look at seperately.