-
Notifications
You must be signed in to change notification settings - Fork 295
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
[v7] Remove cardAddChallenge
#1487
Conversation
let uiType: BTThreeDSecureUIType | ||
let v2UICustomization: BTThreeDSecureV2UICustomization? | ||
|
||
var dfReferenceID: String? |
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.
This is the only property that should need to be a var according to our logic. Updated these and the unit tests with this change. Also confirmed in the demo app things are still appearing as expected.
@@ -108,26 +106,6 @@ class BTThreeDSecureClient_Tests: XCTestCase { | |||
waitForExpectations(timeout: 1) | |||
} | |||
|
|||
func testPerformThreeDSecureLookup_whenCardAddChallengeNotRequested_sendsCardAddFalse() { |
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.
This test was specific to this removed logic in the client:
} else if request._cardAddChallenge == .notRequested {
requestParameters["cardAdd"] = false
}
Co-authored-by: Rich Herrera <ricardherrera@paypal.com>
# Conflicts: # Sources/BraintreeThreeDSecure/BTThreeDSecureRequest.swift
Summary of changes
cardAddChallenge
andBTThreeDSecureCardAddChallenge
Checklist
Authors