-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add new process payment exception #8834
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
hsingyuc
changed the base branch from
develop
to
update/pass-previous-error-to-exception
May 20, 2024 14:11
hsingyuc
force-pushed
the
add/new-process-payment-exception
branch
2 times, most recently
from
May 22, 2024 18:09
7ba3671
to
e1ff53d
Compare
Base automatically changed from
update/pass-previous-error-to-exception
to
develop
May 22, 2024 18:10
hsingyuc
force-pushed
the
add/new-process-payment-exception
branch
2 times, most recently
from
May 24, 2024 18:06
1e2e54f
to
6e1c366
Compare
hsingyuc
requested review from
a team and
leonardola
and removed request for
a team
May 24, 2024 18:10
hsingyuc
force-pushed
the
add/new-process-payment-exception
branch
from
May 29, 2024 01:01
e7a457f
to
80a2ccf
Compare
@leonardola I fixed the unit test and this PR is ready for review. |
leonardola
approved these changes
May 29, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes proposed in this Pull Request
This PR is an extension of the Pass previous Exception with Exception PR. The new_process_payment is still on dev mode only but I think it's still good to have it early on.
The new_process_payment is being used outside of the
try
so this PR pass theNew_Process_Payment_Exception
as previous error with the exception thrown in thenew_process_payment
, so we can use the previous class added in the $additional_data in WC whennew_process_payment
is compatible with Blocks checkout.Note:
new_process_payment
is incompatible with Blocks checkout.Testing instructions
new_process_payment
is incompatible with Blocks checkout.true
throw new Exception( __( 'The payment process could not be completed.', 'woocommerce-payments' ), 0, new New_Process_Payment_Exception() );
innew_process_payment
.process_checkout
The payment process could not be completed.
on the checkout pageWCPay\Exceptions\New_Process_Payment_Exception
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge