v0.23.0

• A sequence once per item: for_each on use. A case made of several steps (create, read back, delete) is a sequence; give its use a for_each, a written list or a data file, and the sequence runs once per item. Each item's keys are params of the sequence, checked like with, and each item saves and reads its own values (spec 0020).

  - use: ../sequences/user-lifecycle.yaml
    for_each:
      - { firstName: Ada, city: Bari }
      - { firstName: Grace, city: Lecce }

    ✓ User lifecycle [1/2] › Create     POST   201     1.08ms  /api/users
    ✓ User lifecycle [1/2] › Read it …  GET    200      554µs  /api/users/35
    ✓ User lifecycle [1/2] › Delete     DELETE 204      665µs  /api/users/35
    ✓ User lifecycle [2/2] › Create     POST   201      674µs  /api/users
    ...
  

  The workflow stops at the first failing step. A variable as the items (for_each: ${users}) is not supported on a use: it stays for call steps. inspect --json gives each step's sequence its item and items.

• Faster inspect and call. The YAML of a workflow is parsed once instead of twice, and the default names of steps no longer recompute their endpoint's placeholders: inspect of 2000 steps went from 443 to 321 ms, of 8000 from 1917 to 1235 ms. The VS Code extension and tinyprobe-app run inspect on every save, so editors get faster too.

• The README is rewritten around what makes tinyprobe different; the command-line reference moved to docs/cli.md, and docs/comparison.md compares tinyprobe with Postman, Bruno and Hurl.

Update: tinyprobe update, or run the install command again.

What's Changed

• Parse a workflow once in inspect and call by @kikutano in #37
• Rewrite the README around what makes tinyprobe different by @kikutano in #38
• A comparison with Postman, Bruno and Hurl by @kikutano in #39
• for_each over a sequence: a use step runs it once per item by @kikutano in #40

Full Changelog: v0.22.0...v0.23.0