- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 02 May 2018 16:09:38 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 2 May 2018 23:10:01 UTC
> This muddles the previously clear path of "always call complete()". Agree, but kinda feel it’s ok here. The code paths all lead to a single `.complete()` call, even if the merchant neends to `retry()`. The flow is still nice: 1. Get response. 1. Validate response. 1. Optionally, retry(): 1. Await things to get fixed user. 1. complete(). -- 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/issues/705#issuecomment-386148882
Received on Wednesday, 2 May 2018 23:10:01 UTC