[Ref] Deprecate Core_Error handling #21279
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] Deprecate Core_Error handling
Before
Too much code to handle something that should not happen
After
Code reduced, deprecation notice added
Technical Details
Core processors throw PaymentProcessor exceptions which is correct - but I DID find that ca.civicrm.contributionrecur returns a
CRM_Core_Error
object - @adixon this PR will add a deprecation notice to that (rareish) flow but you can just throw a PaymentProcessorException insteadI didn't check all of them once I'd established that at least one processor used the old pattern since I'd originally thought we could remove rather than deprecate.
Comments
@mattwire