/* The one way this app talks to its own API. * * const kinds = await api("/api/jobs/kinds"); * await api("/api/jobs", { method: "POST", body: { kind: "tick" } }); * * Every button on every tab goes through `api`, so a failure is always one * toast carrying the server's own sentence. That is the other half of the * bargain the exception handler in `app/main.py` makes: it promises every * error body is `{"detail": ""}`, and this is what * cashes the promise. Wording a failure in the browser as well would be two * descriptions of one thing, and the client's would be the one that was wrong. * * `body` may be a plain object; it is JSON-encoded with the header set, since * forgetting the header is the failure that looks like a server bug. */ (function () { "use strict"; async function api(path, options) { const o = Object.assign({}, options); const headers = Object.assign({ Accept: "application/json" }, o.headers); if (o.body !== undefined && typeof o.body !== "string") { headers["Content-Type"] = "application/json"; o.body = JSON.stringify(o.body); } o.headers = headers; let response; try { response = await fetch(path, o); } catch (e) { // The network, not the server: there is no `detail` to read. window.toast.error("Could not reach the server. Is it still running?"); throw e; } const text = await response.text(); let data = null; if (text) { try { data = JSON.parse(text); } catch (e) { data = null; } } if (!response.ok) { const detail = (data && data.detail) || `The server answered ${response.status} and said nothing about why.`; window.toast.error(String(detail)); const error = new Error(detail); error.status = response.status; error.detail = detail; throw error; } return data; } /* `window.esc` is toasts.js's — it loads first and had to have one anyway, and two copies of an escaper is one of them being fixed. See base.html for the load order that makes this safe. */ /* The queue's own elements do their own fetching, so their failures never pass through `api()`. They raise an event carrying the server's `detail` instead, and this is the same bargain kept one level out: one toast, the server's sentence, nothing reworded here. `desk-jobs:notice` is a notice arriving on the element's socket, which live.js already delivers as `app:notice` — so it is deliberately not listened for. Two toasts for one failure is the bug that listening would buy. */ document.addEventListener("desk-schedules:error", (e) => { const detail = (e.detail && e.detail.detail) || "That change was refused."; window.toast.error(String(detail)); }); window.api = api; })();