Re: [w3c/browser-payment-api] Should a payment request be just data, or a programmable object? (#47)

>From the discussion it seems this issue is unclear on what is being addressed:
 1. Is the issue querying the use of events vs promises?
 1. Is the issue highlighting the need to have a JSON-serializable payment request message that is passed to API (and which the user agent passes on to the payment app) rather than an opaque object with no clarity on how a JSON-serializable payment request message is extracted?

With regards to 1. the current API uses events and the motivations for this provided by @adrianba appear to be uncontested. There is another issue, #51, which discusses the option of a more fluid API shape that is a better place to address this discussion of shape and preferred patterns.

With regards to 2. this is discussed and addressed in the comments on #133.

I am closing this issue and requesting that if there are other issues that were intended to be encapsulated here they be logged as new issues with concrete proposals for addressing them.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/47#issuecomment-211864831