Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337)

Is this referring to these particular steps: 

> Let shippingOptions be the sequence details.shippingOptions.
If the shippingOptions sequence contains multiple PaymentShippingOption objects that have the same id, then set shippingOptions to the empty sequence.
If the shippingOptions sequence contains a PaymentShippingOption that has an amount.value that is not a valid decimal monetary value, then set shippingOptions to the empty sequence.
Copy shippingOptions to the shippingOptions field of target.[[details]].

I'm trying to recall the discussion we had around this. I can't quite recall why we didn't throw. Reading this again, throwing seems good to me. @adrianba do you recall?

-- 
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/337#issuecomment-266877228