tickets

1.3 KB

1. \* One answered request. Handed back by `fetch()` and by `PendingFetch.response()`
2. — never `new`ed. Its shape is exactly what the native side builds
3. (`buildResponse` in fetch.zig): status, ok, url, headers, body, tag, folded in
4. with `>`.
6. RESTORED 2026-08-29 (mission 257). `pending_fetch.hl` has always ended in
7. `r > new FetchResponse()`, but this file was not in the tree — so EVERY
8. `fetch()` and every `.response()` died with a bare `error.UndefinedVariable`
9. at `pending_fetch.hl:42`, which is the second half of the wall the creator
10. hit. It was invisible for the same reason the stale `.so` was: no gate ever
11. ran a fetch against a server it started itself. *\
13. Number status = 0 \\ the HTTP status of the final response (after redirects)
14. Boolean ok = false \\ true for 2xx
15. String url = '' \\ the FINAL url — the last hop of a redirect chain
16. Hybrid headers = {} \\ response headers, names LOWERCASED
17. String body = '' \\ the body as it arrived (empty for a streamed fetch)
18. String tag = '' \\ whatever `tag` the request carried, echoed back
20. // The body as a String. The bytes are already here — this is a reader, not a
21. // second wait — so it is safe to call as often as you like.
22. text() {
23. return body
24. }
26. // The body parsed as JSON. A body that is not JSON raises, like JSON.parse
27. // anywhere else; `on Error` catches it.
28. json() {
29. return JSON.parse(body)
30. }