-
Notifications
You must be signed in to change notification settings - Fork 237
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
Rename Google Pay APIs #824
Conversation
@@ -200,63 +189,55 @@ public void requestPayment(@NonNull final GooglePayRequest request, | |||
|
|||
//noinspection ConstantConditions | |||
if (request == null) { | |||
callback.onGooglePayIntentData(null, new BraintreeException( |
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.
Random 🤔 : There may be a benefit to having on<PAYMENT_METHOD>Result()
style callbacks. It would help in the extreme case that a merchant decides to implement multiple payment method listener interfaces on the same class. If they're all named the same it could get confusing. It's more verbose, but for single response objects they'll be shortened to lambdas on Java 8 and up.
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.
Good point - I'll plan to refactor the naming of these methods in the PRs that move to single result object callbacks to make sure that the naming all makes sense.
Summary of changes
createPaymentAuthRequest
andtokenize
and rename associated result objects and callbacksChecklist
Authors