Skip to content
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

Modify interface to allow client to choose which service to connect to #9

Merged
merged 1 commit into from
May 28, 2020

Conversation

mgiuca
Copy link
Member

@mgiuca mgiuca commented May 27, 2020

The payment method identifier is now given as a parameter to getDigitalGoodsService, rather than returned as a property. This allows the user agent to expose multiple services, letting the client choose which one to use.

Closes #1.
Closes #8.

The payment method identifier is now given as a parameter to getDigitalGoodsService, rather than returned as a property. This allows the user agent to expose multiple services, letting the client choose which one to use.

Closes WICG#8.
@mgiuca
Copy link
Member Author

mgiuca commented May 27, 2020

@danyao @phoglenix PTAL

(I can't add you as a reviewer until you accept invite.)

Copy link
Collaborator

@phoglenix phoglenix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@marcoscaceres
Copy link
Contributor

Probably want to move getDigitalGoodsService() to be a static method on PaymentRequest? We will need to figure out how this interfaces with Payment Handler API.

@mgiuca
Copy link
Member Author

mgiuca commented May 27, 2020

@marcoscaceres Maybe... but for now, I am considering this as a separate feature to PR. It seems less controversial that way, than trying to add it into this existing API which is about more general payment flows.

@danyao
Copy link
Collaborator

danyao commented May 27, 2020

LGTM!

@mgiuca mgiuca merged commit 9f0bb2f into WICG:master May 28, 2020
@danyao danyao mentioned this pull request May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non-Platform Digital Goods Services Should paymentMethods be an array rather than a single string?
4 participants