Separate getStatusMessage function #27015
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
Separate
getStatusMessage
functionBefore
Parent & child class use the same
getStatusMessage
function but follow different paths within itAfter
Child class implements the function itself, functionality separated
Technical Details
The CRM_Event_Form_Task_Register form was once part of CRM_Event_Form_Participant
It now extends it & the goal is to disentangle it from the parent.
In general _single is only set for the parent & describes actions for that whereas the Register form is a task that can act on many
Comments