ToolsCommandsCommands for records, findings and review
jadpo records
On this page
List and update the records.
Every file Jadpo generates and the project commits is a record (area 18): each API's api/jadpo records lists them by the command that writes them, each with whether it is up to date, and fails while one is not, naming the command to run. update brings every record up to date at once: each API record written from the routes, each other record rewritten sorted and in the newest format, and a record under its old name moved.
jadpo records [action]Arguments
action(optional): What to do: update, or nothing to list them
On every command
--json: Print data for tools instead of text--full: Show everything a report shortens--help: Show every flag, with examples--color <when>: Choose when to use colour
jadpo records --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("records"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.
Examples
# See every record and whether it is up to datejadpo records# Bring every record up to datejadpo records update
Errors
cli.records_arguments: Ajadpo recordscommand names an action other thanupdaterecord.edited: Generated record was edited by handrecord.format_newer: A record file in the project was written by a newer Jadpo, in a format this one can't readrecord.out_of_date: A record file that Jadpo writes from your code is missing, or no longer matches the codetoolchain.artifact_write_failed: A file Jadpo writes for you, such as a record, couldn't be written, usually because it or its folder is read-onlytoolchain.project_not_found: You ran a command that works on a project in a folder with noapp.jadpo, in it or in any folder above it
Markdown for agents: /docs/jadpo-records.md.Built from Jadpo main at aee2e8f.