- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 12 Nov 2019 21:02:28 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 November 2019 05:02:30 UTC
As I was just reviewing this... I... um... had a thought...🤔 what if: ```JS typedef (sequence<AddressParts> or boolean) AddressRequirement; dictionary PaymentOptions { AddressRequirement requestBillingAddress = false; AddressRequirement requestShippingAddress = false; }; ``` That would: * retain backwards compatibility with 1.0 (sequence just gets coerced to `true` in 1.0 implementations). * it avoids the `{ requestShippingAddress: false, requestShippingAddressParts: ["country"] }` developer pitfall. * avoid adding adding extra members WDYT? (`AddressRequirement` is a terrible name... we can change that.) -- 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/payment-request/pull/873#issuecomment-553240357
Received on Wednesday, 13 November 2019 05:02:30 UTC