-
Notifications
You must be signed in to change notification settings - Fork 658
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
Pass GooglePayLauncher arguments to DefaultGooglePayRepository
#4157
Conversation
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.
Does it need to be fixed in GooglePayPaymentMethodLauncher
too?
Diffuse output:
APK
DEX
|
DefaultGooglePayRepository
GooglePayJsonFactory.BillingAddressParameters(), | ||
true, |
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.
So for Payment Sheet we'll always require an existing Payment Method? I know this is the existing behavior, but thinking that we could set to false so Google Pay will still be an option and the user can add the Payment Method during checkout.
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.
I think we should give developer more control, so he/she can manage the flow
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.
I did ask this question. The plan for now is to match iOS.
Summary
Arguments from GooglePayLauncher were not being pass through to the DefaultGooglePayRepository. Also added a class for a GooglePayLauncher playground. This is not exposed in the launcher list so as not to confuse users on how to integrate.
#4155
Testing