Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413)

:-1: to nullable at the front of the constructor, because we don't have the data to backup the intuition of many clients using the new field. Let's use the `optional` keyword. OK to keep at the front. In practice this means that there will be 4 constructors:

    PaymentRequest(PaymentMethodData methodData, PaymentDetails details);
    PaymentRequest(PaymentMethodData methodData, PaymentDetails details, PaymentOptions options);
    PaymentRequest(DOMString id, PaymentMethodData methodData, PaymentDetails details);
    PaymentRequest(DOMString id, PaymentMethodData methodData, PaymentDetails details, PaymentOptions options);

-- 
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/pull/413#issuecomment-278114314

Received on Tuesday, 7 February 2017 19:32:43 UTC