-
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] Update BTThreeDSecureRequest
Parameters
#1452
[v7] Update BTThreeDSecureRequest
Parameters
#1452
Conversation
BTThreeDSecureRequest
Required ParametersBTThreeDSecureRequest
Parameters
BTThreeDSecureRequest
ParametersBTThreeDSecureRequest
Parameters
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.
One comment but it's not a blocker. Approving ahead of time.
accountType: BTThreeDSecureAccountType = .unspecified, | ||
additionalInformation: BTThreeDSecureAdditionalInformation? = nil, | ||
billingAddress: BTThreeDSecurePostalAddress? = nil, | ||
_cardAddChallenge: BTThreeDSecureCardAddChallenge = .unspecified, |
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.
nit: we can probably just leave this out of the init for now then remove it in the ticket to remove the property completely. If that's more work than it's worth though, feel free to leave and we can hopefully pick up that cleanup ticket soon!
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.
👏
Summary of changes
BTThreeDSecureRequest
properties to have everything in the init vs using dot syntaxChecklist
Authors