Skip to content

wiretap v0.2.7

Choose a tag to compare

View all tags
@plutack plutack released this 10 Sep 16:44
· 45 commits to main since this release
v0.2.7
422d126
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

wiretap v0.2.7

This release adds explicit compose recipes for niche replay workflows while
preserving the general-purpose request composer introduced in v0.2.6.

Source recipes

Create a normal transform with the new on_compose trigger, then select it in
Compose > Source recipe. Paste source text or import a JSON file, choose a
target base URL, and run the recipe. The script receives the source as
request.body and can construct the complete method, URL, headers, and body.

Applying a recipe performs no network I/O. The result opens in the manual
composer, where every generated field is visible and editable before Send is
pressed. Automatic on_replay transforms are disabled for a generated draft
until the user explicitly opts back in.

Recipes are stored locally in the existing transform database and are selected
per preparation. Wiretap ships no provider-specific runtime behavior. A small,
provider-neutral source-record example is documented in the
recipe file.

Composer layout

The Compose workspace now has separate Manual request and Source recipe
modes. The manual view has focused Body and Headers tabs paired with a response
inspector, and it collapses cleanly for narrower windows. Opening a transform
from the sidebar keeps Compose visible beside it.

Every transform trigger now has an editable sample request test bench. Method,
URL, headers, body, and response status can be supplied in the transform editor,
and the transformed request is shown without touching the network.

The existing manual composer, request-envelope import, webhook and traffic
handoff, optional on_replay chain, and bounded response inspection remain
available.

Safety and compatibility

  • Recipe application cannot send an HTTP request.
  • Recipe targets and generated destinations must be absolute HTTP(S) URLs.
  • Disabled recipes do not appear in the composer.
  • Existing scripts and databases require no migration.
  • The scripting sandbox remains filesystem-free and network-free with a
    five-second execution timeout.

Quality

Application and GUI-binding tests cover recipe discovery, enabled-state
filtering, source transformation, headers, draft safety, rejection, and URL
validation. The full Go suite, frontend syntax checks, generated Wails
bindings, and GUI build pass for this release.

Full changelog: v0.2.6...v0.2.7

Assets 10
Loading