Skip to content

JSON Analyzer v0.1.11 - The Curl Lens Sharpens

Choose a tag to compare

@github-actions github-actions released this 08 Jun 19:18
· 5 commits to main since this release

JSON Analyzer v0.1.11 - The Curl Lens Sharpens

The Quest

Curl Executor had become general-purpose, but the last steps still needed a sharper eye. HTTP errors should be visible responses, and batch setup should make common path and query replacements easy without guessing domains or mutating the wrong URL.

What Awoke

  • Single curl execution now shows non-2xx HTTP responses with status, headers, formatted body preview, copy response, and copy details instead of treating them as missing-url or parse failures.
  • Batch setup can detect URL path segments and query parameters from the actual request URL and insert generic placeholders for selected targets.
  • Query-parameter insertion now preserves raw URL text, duplicate parameter order, encoded names, fragments, empty values, and valueless parameters.
  • Curl URL detection now follows a span-aware argument parser for supported curl options, including quoted and inline --url values, multiline Postman curl commands, and safe rejection of ambiguous unsupported URL options.
  • Batch result handling now counts HTTP 4xx and 5xx responses as failed items while preserving their response payloads and input value traceability.
  • Curl response spacing, typography, status badges, and body previews were tightened for easier scanning.

Runes of Assurance

  • pnpm -C frontend run test -- App.curl.test.tsx --runInBand passed with 114 tests.
  • pnpm -C frontend run typecheck passed.
  • pnpm -C frontend run lint passed.
  • pnpm -C frontend run build passed.
  • git diff --check passed.
  • Neutral-language scans found no domain-specific wording in curl-related implementation and tests.

Known Boundaries

  • Rust format, clippy, and test checks could not be run on this workstation because cargo and rustfmt were not available on PATH.
  • Batch replacement remains intentionally raw and exact. Users should provide already-encoded values for URL paths or query strings.
  • Curl jobs remain in-memory only; durable job history is still deferred.
  • The APT repository currently publishes Linux amd64 packages only.