Code editor
Fetchpier uses a rich editor for raw request bodies and pre-request or post-response scripts. URL and
structured request fields also provide {{variable}} suggestions and highlighting.
Request-body editing
Section titled “Request-body editing”Raw JSON, XML, HTML, JavaScript, and text bodies support:
- syntax highlighting selected from the raw subtype or detected content;
- line numbers, folding, bracket matching, search, and replace;
- on-demand beautification for JSON and XML;
- variable completion and distinct colors for resolved, dynamic, and unknown tokens.
Choose an editor theme family independently of the application theme:
| Family | Variants |
|---|---|
| Default | Native light and dark palettes. |
| GitHub | Light and dark. |
| One Dark | Dark; falls back to the native light editor in light mode. |
| Dracula | Dark; falls back to the native light editor in light mode. |
The family preference persists across launches.
Script assistance
Section titled “Script assistance”Script editors add language assistance derived from the same fp.* type contract used to generate
the scripting API reference:
- member and parameter completion with kind-specific icons;
- hover documentation;
- inline type, unused-identifier, and deprecation diagnostics;
- recent completions promoted in the suggestion list;
- strikethrough for deprecated members.
Typing is phase-aware. fp.response is unavailable in a pre-request script, and request properties
that become read-only after the send are diagnosed in a post-response script.
The editor deliberately exposes the sandbox, not browser or Node.js globals. It does not suggest
window, the DOM, Promise, timers, filesystem functions, or network APIs because the runtime would
reject them. A clean editor does not guarantee a successful request, but it catches many API and
phase mistakes before execution.