Skip to content

Conversation

adrianba
Copy link
Contributor

PaymentItems are only used for display and we don't currently have a
reason to provide an id. Since this is a dictionary, developers can add
whatever fields they want but requiring an ID is unnecessary.

PaymentItems are only used for display and we don't currently have a
reason to provide an id. Since this is a dictionary, developers can add
whatever fields they want but _requiring_ an ID is unnecessary.
@rvm4
Copy link
Collaborator

rvm4 commented Apr 27, 2016

Sounds good to me

@rvm4 rvm4 merged commit c536e57 into w3c:gh-pages Apr 27, 2016
@adrianhopebailie
Copy link
Collaborator

LGTM

@adrianba adrianba deleted the remove-item-id branch April 28, 2016 15:39
adrianba added a commit to adrianba/browser-payment-api that referenced this pull request Apr 28, 2016
PRs w3c#158, w3c#160, and w3c#161 made changes that affect the examples. These
weren't reflected in original PRs to keep those changes simple and to
avoid merge conflicts from changing the same lines in the spec. This
changes updates the examples.

Also updating the syntax to be consistent and use JavaScript (rather
than JSON).

Fixes w3c#164.
adrianba added a commit that referenced this pull request Apr 28, 2016
PRs #158, #160, and #161 made changes that affect the examples. These
weren't reflected in original PRs to keep those changes simple and to
avoid merge conflicts from changing the same lines in the spec. This
changes updates the examples.

Also updating the syntax to be consistent and use JavaScript (rather
than JSON).

Fixes #164.
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.

3 participants