Are we sure we want to take an object as input, not an existing JSON string? If we are (e.g. if callers are expected to construct the object on the fly instead of producing it from JSON to start with), it would be good to sort out https://github.com/w3c/browser-payment-api/issues/346 and https://github.com/w3c/browser-payment-api/issues/338 too so the processing model is actually defined. It's hard to write a useful PR without knowing what should happen to the string after it's generated. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/307#issuecomment-265307254
Received on Tuesday, 6 December 2016 23:32:09 UTC