Closed serhii-tkachenko closed 3 weeks ago
I feel we need to refactor these strategies separately to braintree ones, since with this approach we will have to pass braintree sdk everytime. Maybe its better to have a separate strategy.
I feel we need to refactor these strategies separately to braintree ones, since with this approach we will have to pass braintree sdk everytime. Maybe its better to have a separate strategy.
IMO In terms of maintenance its better to pass 1 extra class instead of creating separate strategies. I don't think it affects overall apple pay performance for other apple pay gateways... so it we might think about it when we have to inject some specific to other provider code
What?
Updated apple pay strategies with
BraintreeSdk
class instead ofBraintreeIntegrationService
Why?
BraintreeIntegrationService
is deprecated, so to be able to remove it in the future apple pay strategies should be updatedTesting / Proof
Manual tests:
Unit tests CI