Skip to content

Conversation

@joshheald
Copy link
Contributor

@joshheald joshheald commented Dec 6, 2022

Part of: #8321

Description

As per the proposal in pdfdoF-1My-p2, this PR duplicates the PaymentCaptureOrchestrator for use in the refactored and updated payment flows, as we add support for the built-in card reader in project sTAP Away.

There are no functional changes to either flow in this PR, it is purely preparatory for #8329

Testing instructions

Run unit tests

Check you can take a payment with the feature toggle in experimental features off and on.


  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@joshheald joshheald added type: task An internally driven task. feature: mobile payments Related to mobile payments / card present payments / Woo Payments. status: feature-flagged Behind a feature flag. Milestone is not strongly held. labels Dec 6, 2022
@joshheald joshheald added this to the 11.6 milestone Dec 6, 2022
@joshheald joshheald changed the title Issue/8321 duplicate payment capture orchestrator for refactor [Mobile Payments] Duplicate PaymentCaptureOrchestrator for refactor Dec 6, 2022
@joshheald joshheald changed the base branch from trunk to issue/8295-tap-on-mobile-errors December 6, 2022 17:26
@wpmobilebot
Copy link
Collaborator

You can test the changes from this Pull Request by:
  • Clicking here or scanning the QR code below to access App Center
  • Then installing the build number pr8328-361f4cc on your iPhone

If you need access to App Center, please ask a maintainer to add you.

@joshheald joshheald marked this pull request as ready for review December 6, 2022 17:55
@joshheald joshheald requested a review from toupper December 6, 2022 17:55
@toupper toupper self-assigned this Dec 7, 2022
/// 3. Obtain a Payment Intent from the card reader (i.e., create a payment intent, collect a payment method, and process the payment)
/// 4. Submit the Payment Intent to WCPay to capture a payment
/// Steps 1 and 2 will be implemented as part of https://github.com/woocommerce/woocommerce-ios/issues/4062
final class LegacyPaymentCaptureOrchestrator {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like your approach when dealing with legacy code here, smaller PRs and meaningful renaming 👏

@toupper
Copy link
Contributor

toupper commented Dec 7, 2022

The code looks good and it tests well 🎉 :shipit:

Base automatically changed from issue/8295-tap-on-mobile-errors to trunk December 7, 2022 13:05
@peril-woocommerce
Copy link

Warnings
⚠️ This PR is assigned to a milestone which is closing in less than 2 days Please, make sure to get it merged by then or assign it to a later expiring milestone

Generated by 🚫 dangerJS

@joshheald joshheald merged commit cc9ae29 into trunk Dec 7, 2022
@joshheald joshheald deleted the issue/8321-duplicate-payment-capture-orchestrator-for-refactor branch December 7, 2022 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature: mobile payments Related to mobile payments / card present payments / Woo Payments. status: feature-flagged Behind a feature flag. Milestone is not strongly held. type: task An internally driven task.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants