Skip to content

# @disabled and # @sleep <duration> directives #32

Closed

Description

@dataGriff

Why

httpyac parity, and two small things people reach for: keeping a request in a file without it running in the flow, and pausing before a request against a rate-limited API.

What

  • # @disabled: the request is skipped when its file runs as a flow, by a (run all) in the UI, by I run the file in features and by MCP run_file. apic run <id> still sends it (the user asked for it by name). list marks it (dimmed in the UI, "disabled": true in --json); flow output shows skipped (disabled).
  • # @sleep <duration>: wait that long before sending. Shown in describe. Cancellable.
  • Both are warnings-free in validate; a bad duration is an error.

Where

internal/httpfile/parse.go, ast.go, internal/runner/runner.go (RunAll), internal/ui/list.go, internal/bdd/steps.go, internal/mcp/server.go, internal/cli/inspect.go (list).

Docs

docs/format.md, docs/cheatsheet.md, docs/cli.md (list JSON field).

Tests

Parser cases; a flow test where the disabled request is skipped and counted; a direct run of a disabled request; a sleep test with a fake sleeper.

Activity

  1. added a commit that references this issue on Sep 24, 2026
  2. dataGriff commented on Sep 24, 2026

    @dataGriff
    OwnerAuthor

    Done in #115 (ef86a3f). # @disabled keeps a request out of flows (apic run file.http, the UI's f/a, When I run the file, MCP run_file), which report it as skipped (disabled); naming it still sends it. # @sleep <duration> waits before sending and can be cancelled. list, describe and validate (bad-sleep) know both. See "Pauses and disabled requests" in docs/format.md.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions