registry-render validate command reference
Dry-run request data against a document’s schema, without rendering.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.
registry-render validate [OPTIONS] --bundle <BUNDLE> --type <DOCUMENT> --data <DATA>Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--bundle <BUNDLE> | Yes | n/a | n/a | n/a | Authored bundle or package directory |
--type <DOCUMENT> | Yes | n/a | n/a | n/a | Document type id, as declared in the manifest |
--data <DATA> | Yes | n/a | n/a | n/a | JSON file holding the bare data object |
--locale <LOCALE> | No | n/a | n/a | n/a | Primary locale, recorded in the envelope; must be one the document declares. The template receives every label table either way |
--format <FORMAT> | No | human | human, json | n/a | Emit the selected command’s finite report in this format |
-h, --help | No | n/a | n/a | n/a | Print help (see a summary with ‘-h’) |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.