Store data

Write the data of the current state (as data export gives it) as JSON Lines, one element per line, to <commit>.jsonl in a folder; -dirty with uncommitted ReqSeq files, replaces the file of the same commit; an old <commit>.json stays as it is. Many such files load as one table, grouped by commit and dirty. One folder per selection: the name is the same for every selection. Takes selection.baseline as data export does.

Command data.store. Writes files in the working tree, never to Git. It is refused while the workspace is read-only. Stores the data of the current state with the versions of its elements, which depend on the metamodel (which properties count).

Input

Field	Type	Required	Description
folder	localPath	yes	Folder for the file; created when missing inside a repository of the workspace (also an ignored one), must exist outside.
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

Field	Type	Required	Description
files	array of string	yes
problems	array of problem	no

App

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

CLI

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

Usage: reqseq data store <folder> [options]

Write the data of the current state (as data export gives it) as JSON Lines, one
element per line, to `<commit>.jsonl` in a folder; `-dirty` with uncommitted
ReqSeq files, replaces the file of the same commit; an old `<commit>.json` stays
as it is. Many such files load as one table, grouped by `commit` and `dirty`.
One folder per selection: the name is the same for every selection. Takes
`selection.baseline` as `data export` does.

Arguments:
  folder                  Folder for the file; created when missing inside a
                          repository of the workspace (also an ignored one),
                          must exist outside.

Options:
  --folder <value>        instead of the argument <folder>
  --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
  -h, --help              show help

Only via --input: selection

API

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

MCP

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