Save ReqIF mapping
Save or change the mapping of a source to the own metamodel, in the mapping folder (default reqif).
Command reqif.saveMapping. Writes files in the working tree, never to Git. It is refused while the workspace is read-only. Maps a source to the own metamodel, which is missing or faulty.
| Field | Type | Required | Description |
|---|---|---|---|
mapping |
reqif-mapping |
yes | Mapping of the types and attributes of one ReqIF source to the own metamodel, saved as YAML in the mapping folder of the workspace (mappings, default reqif in the main repository) and reused for every later import from and export to that source (N-045, D-022, SR-054). The own metamodel is never changed by it (SR-054 AK3). Also holds saved export profiles (SR-059 AK3). |
file |
localPath |
no | Inside the mapping folder of the workspace, for every access; default the portable source name. |
Output
Section titled “Output”| Field | Type | Required | Description |
|---|---|---|---|
files |
array of string |
yes | |
problems |
array of problem |
no |
In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Save ReqIF mapping.
reqseq reqif save-mapping, with --json for the output as JSON. Its help:
Usage: reqseq reqif save-mapping [options]
Save or change the mapping of a source to the own metamodel, in the mappingfolder (default `reqif`).
Options: --file <value> Inside the mapping folder of the workspace, for every access; default the portable source name. --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: mappingPOST /v1/commands/reqif.saveMapping on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.
Tool reqif_saveMapping of the MCP server (reqseq mcp), with the input as its arguments.