One problem with this is that it seems to constrain us now to only Boolean values that can be optional. What if we want an option that can be an enum with multiple options.
Also, passing
`{ request: [{name: "shippingAddress"}, {name: "email",optional:true}, {name: "phone-number",optional:true}] }`
seems a lot less friendly than
`{ requestShipping:true, requestEmail:"optional", requestPhoneNumber:"optional" }`
The latter seems less complex and is more flexible.
---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/65#issuecomment-211977071
Received on Tuesday, 19 April 2016 15:25:22 UTC