| 00:37 | <ser.bicer@hotmail.com> | valid connected account request |
| 06:27 | <Noam Rosenthal> | Noam Rosenthal: for the case where body is null we also cannot queue a task I think as that will be observable, at least in theory that promise resolves in the task that gets hold of it package data in their corresponding functions instead of a big switch-case, I think it's cleaner now, and the task thingy is sorted. |
| 15:12 | <Noam Rosenthal> | Andreas Kling: as per your report, consuming the body in fetch doesn't need promises anymore. |
| 18:38 | <jugglinmike> | annevk: Domenic I don't know if it matters much, but the return value of parse a JSON string to an infra value seems inconsistent to me. Rather than always returning a completion record, it returns an "throw" completion record on failure and a infra value on success |
| 18:43 | <jugglinmike> | I only know of two call sites: HTML and WebDriver BiDi. HTML's wording seems fine with this https://html.spec.whatwg.org/multipage/webappapis.html#parse-an-import-map-string |
| 18:44 | <jugglinmike> | WebDriver BiDi is a little more ambiguous--"if [the algorithm] throws an exception" https://w3c.github.io/webdriver-bidi/#handle-an-incoming-message |
| 18:50 | <jugglinmike> | Or if ECMAScript's implicit normal completion applies, then maybe HTML's call site just needs a tweak |