Remove AuthenticationComponent Handling of ThreeDS2FingerprintAction & ThreeDS2ChallengeAction (part 3/4)#2502
Conversation
…ing into compact flow
|
ℹ️ No baseline data found for 'develop'.
|
There was a problem hiding this comment.
Code Review
This pull request removes the legacy 3DS2 "classic" flow, deleting ThreeDS2ClassicActionHandler and consolidating 3DS2 actions. Feedback identifies a potential regression where paymentData is no longer propagated in 3DS2 actions, resulting in nil values in integration tests. Additionally, suggestions were made to use package visibility for ThreeDSResult and the Error enum to maintain consistency with the AuthenticationComponent and facilitate cross-module access.
|
| ❌ | 4 Removals |
Adyen
Action
❌ Removed
case threeDS2Challenge(Adyen.ThreeDS2ChallengeAction)case threeDS2Fingerprint(Adyen.ThreeDS2FingerprintAction)AdyenActions
❌ Removed
public enum ThreeDS2Details: Adyen.AdditionalDetailspublic struct ThreeDSResult: Swift.DecodableAnalyzed targets: Adyen, AdyenActions, AdyenCard, AdyenCardScanner, AdyenCashAppPay, AdyenCheckout, AdyenComponents, AdyenDelegatedAuthentication, AdyenDropIn, AdyenEncryption, AdyenSession, AdyenSwiftUI, AdyenTwint, AdyenUI, AdyenWeChatPay
Summary [Required]
Whats next?
COSDK-1100
Checklist [Required]
Previous PR