Skip to content

Fiber v0.13.0

Choose a tag to compare

@github-actions github-actions released this 22 Aug 20:54
50fa88f

Minor Changes

  • #59 68ab80c Thanks @MathiasWP! - Richer OpenAPI (tags as folders, path and query parameters, operation descriptions, response-schema checks), per-collection HTTP identity (cookie jar, timeout, redirects, proxy, invalid certs), and non-JSON bodies (form, multipart, file). Query parameters are available on every method.

Patch Changes

  • #66 d24f8d8 Thanks @MathiasWP! - Harden MCP credential boundaries, concurrent request handling, response storage, endpoint discovery, and protocol validation.

  • #60 33fdf99 Thanks @MathiasWP! - Creating a collection now shows its first request immediately. The new section was mutated as a plain object after $state had already proxied it, so the sidebar never saw the push.

  • #60 33fdf99 Thanks @MathiasWP! - Importing an OpenAPI spec now reports how many endpoints were actually added. The count used to re-read a live list after those endpoints had already been pushed, so it always said zero.

  • #63 bfbfcd0 Thanks @MathiasWP! - A few performance fixes: computing what a loader refresh added or removed was quadratic in the number of endpoints, sending a request whose body comes from a file blocked the async runtime instead of reading it off-thread, and the sidebar's "Move to" submenu recomputed its target list twice per request row.

  • #64 749d148 Thanks @MathiasWP! - Obvious performance wins on both sides of the glass. The URL preview no longer round-trips to Rust on every keystroke. ⌘K and collapsed collections stop rebuilding every loaded endpoint in the background. Schema validation and placeholder highlighting skip bodies too large to be worth it. Loader samples are no longer pretty-printed whole just to show the first 20 KB. Streamed chunks are joined rather than concatenated, and a large response is not shipped over IPC a second time after it has already streamed. Collections stay in memory after the first read so a send does not re-parse every saved body; the MCP server does the same across tool calls. History deletes and section deletes no longer run on the UI event-loop thread. A send with static auth no longer clones the request body just in case a 401 retry needed it.

  • #56 94f8b39 Thanks @MathiasWP! - Svelte 5 best practices: $state.raw for wholesale-replaced data (loader caches, OpenAPI samples, browser snapshots), {@attach} in place of actions and the CodeMirror mount effect, and window listeners on <svelte:window> rather than inside $effect.