Skip to content

JSON Analyzer v0.1.12 - The Batch Compass Learns the Shape

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Jun 20:43
· 4 commits to main since this release
v0.1.12
5243eee

JSON Analyzer v0.1.12 - The Batch Compass Learns the Shape

The Quest

Batch mode no longer needed only to be general-purpose; it needed to feel obvious before the first request was sent. The old 1 and 2 sample values were too vague for real REST work, especially when a pasted Postman curl already showed whether the selected target looked like a UUID, number, email, date, slug, or token.

What Awoke

  • Curl Executor now starts with neutral UUID-style batch examples instead of ambiguous numeric placeholders.
  • Batch setup now generates editable example values from the selected URL path segment or query parameter shape.
  • Generated examples cover UUIDs, integers, email addresses, dates, timestamps, slugs, token-like values, encoded query values, empty values, and unknown strings.
  • User-entered batch values are preserved when switching batch targets; generated examples update only while the field is still auto-managed.
  • Clearing the form now resets the auto-example tracker so a newly pasted curl can repopulate smart examples correctly.
  • Stale domain-specific wording was removed from touched docs so Curl Executor remains framed as a generic REST API tool.

Runes of Assurance

  • npm --prefix frontend run test -- App.curl.test.tsx src/components/curl-executor/utils.test.ts passed with 49 tests.
  • npm --prefix frontend run typecheck passed.
  • npm --prefix frontend run lint passed.
  • npm --prefix frontend run test passed with 127 tests.
  • npm --prefix frontend run build passed.
  • git diff --check passed.
  • Neutral-language scans found no blocked domain-specific wording in source, tests, docs, release notes, README, or package metadata touched by this release.

Known Boundaries

  • Batch replacement remains intentionally raw and exact. Users should provide already-encoded values for URL paths or query strings.
  • Example generation is shape-based only; it does not infer route semantics or API-specific entity names.
  • Rust format, clippy, and test checks could not be run on this workstation because cargo and rustfmt were not available on PATH.
  • Curl jobs remain in-memory only; durable job history is still deferred.
  • The APT repository currently publishes Linux amd64 packages only.
Assets 11
Loading