-
-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REF][Test] Remove call to CRM_Contribute_BAO_Contribution::recordAdditionalPayment in favour of payment create #14137
Conversation
(Standard links)
|
that's weird - it succeeded but didn't update github....
|
test this please |
e8528fd
to
db18668
Compare
…nt in favour of payment create
@monishdeb @pradpnayak @jitendrapurohit anyone want to take a look? With this merged the only gaps for using Payment.create for refunds from the form are the activity - a step on that is here #14269 and the participant status handling - which is odd but... |
Yup happy with this patch, tested on my local and it worked fine. Also the added tests passes. Merging it now |
Overview
Remove call to CRM_Contribute_BAO_Contribution::recordAdditionalPayment in favour of using Payment.create api. This exposes that the Payment.create api currently adds an extra transaction for refunds where the status is changed to completetransaction & handles that
Before
Less tests. Extra financial trxn created when adding a refund payment through the Payment.create api
After
More tests. Extra financial trxn not created when adding a refund payment through the Payment.create api
Technical Details
The goal here is to remove recordAdditionalPayment and call the Payment.create api instead. In order to do this we have been working to ensure the functionality is equivalent and tested.
With this merged I still see 2 gaps
Comments
FYI @pradpnayak @jitendrapurohit @monishdeb