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.34.0 and catalog SHA-256 521175a69262e60df96745886392348e5bb8d82e63cdd24bdf4baa80d46e5ff4. 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 | Bundle 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 |
--json | No | n/a | n/a | n/a | Machine-readable result on stdout (failures: problem+json on stderr, typed exit code) |
-h, --help | No | n/a | n/a | n/a | Print help |
Generation contract
Section titled “Generation contract”Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.