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

I was comparing the code snippets in the original comment. In the first snippet, which calls the PaymentRequest constructor, the only programmable object is the PaymentRequest object. In the second code example, there is no programmable object. A promise is returned. Since the issue asks whether a programmable object should be involved I concluded that the comparison was between code that returned an object and code that didn't but returned a promise. Hence my comment.

All of the arguments to the current PaymentRequest constributor can be serialized as JSON. In fact that is a requirement for some of them. None of them are "programmable". There is also a separate issue (#15) about combining arguments into a JSON serializable object.

As you say, we've already adopted a design with a programmable object. Another reason I think this issue should be closed.

---
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-211570344