messagingctl generate templates command reference
Write every checked template version’s locale and data contract.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.
messagingctl generate templates [OPTIONS] --project <DIRECTORY> --output <FILE>Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--project <DIRECTORY> | Yes | n/a | n/a | n/a | Editable Messaging project holding messaging.yaml |
--output <FILE> | Yes | n/a | n/a | n/a | New JSON file to create. Existing files are never overwritten |
--format <FORMAT> | No | human | human, json | n/a | Emit the selected command’s report in this format |
-h, --help | No | n/a | n/a | n/a | Print help |
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.