[REF] dev/core#2790 Pre process cleanup on pdf tasks #21310
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
[REF] Pre process cleanup on pdf tasks
Before
Three variables are set on the class that were originally set because of shared code but don't seem to make sense
$form->_single
- this was presumably an enotice fix - if any enotices re-emerge we can fix the right way - by setting a property on the form$form->_contactIds
- I believe this was added to support the invoice form - it doesn't make sense to default to writing a letter to your self$form->_emails
- this is used in the emails classes but not the pdf classes on searchingAfter
Poof
Technical Details
Comments
@demeritcowboy this is the clean up I thought needed to be done.... With this done I'll move the preProcess to the trait & move the default setting into it's own function or, more likely, into the setDefaults function already on the trait