Re: [w3c/browser-payment-api] Change the way we request user data (#65)

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

Making that member boolean is just a proposal, it could be a string or an enum.

#145 makes the case for this being a lot more flexible than the current spec allows.

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