Skip to content
ReqSeq

Export data

Data of the current state as JSON for external evaluation, or, from the command line and the API, as JSON Lines with one element per line: every element unless a selection is given, so an evaluation selects by filter, package, baseline or variant instead of exporting everything; no paging. With data store the only commands so far that take selection.baseline: the elements the baseline lists, as they are now. data store writes a whole state to a file.

Command data.export. Reads the workspace and changes no file.

Input

Section titled “Input”
Field Type Required Description
selection selection no Which elements a command works on: a saved filter, an inline filter, a package, a baseline or explicit IDs, optionally seen through a variant view.

Output

Section titled “Output”

No output fields.

App

Section titled “App”

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Export data.

CLI

Section titled “CLI”

reqseq data export, with --json for the output as JSON. Its help:

Usage: reqseq data export [options]


Data of the current state as JSON for external evaluation, or, from the command
line and the API, as JSON Lines with one element per line: every element unless
a selection is given, so an evaluation selects by filter, package, baseline or
variant instead of exporting everything; no paging. With `data store` the only
commands so far that take `selection.baseline`: the elements the baseline lists,
as they are now. `data store` writes a whole state to a file.


Options:
  --input <json|@file|->  command input as JSON: inline, from a file, or from
                          standard input
  --workspace <path>      workspace root (default: nearest folder upwards with
                          reqseq-workspace.yaml)
  --json                  print exactly the command output as JSON
  --yaml                  print the whole command output as YAML, problems one
                          per line
  --jsonl                 print the output as JSON Lines: one line per item of
                          elements, each with reqseq-data, commit, dirty first
  -h, --help              show help


Only via --input: selection

API

Section titled “API”

POST /v1/commands/data.export on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

MCP

Section titled “MCP”

Tool data_export of the MCP server (reqseq mcp), with the input as its arguments.