Enum JsonMode 

#[non_exhaustive]
pub enum JsonMode {
    Artifact,
    Supported,
}

How a subcommand interacts with --mode json.

Wire shape: every variant serialises to an object with a status discriminant, so a consumer sees uniform {"status":"…", …} records (#[serde(tag = "status")]). Before #215 the previous mixed string/object representation forced consumers to handle two JSON shapes for sibling variants.

Tuple variants not permitted. #[serde(tag = "status")] requires the tag to live in the same flat object as variant fields; tuple variants are incompatible with internally-tagged representation. Future variants MUST use named fields.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Artifact

The command’s primary output IS the requested artifact, not informational chatter. --mode is informational here; the exact stdout shape (e.g. JSON for csl / graph / capabilities and the JSON-RPC stream from serve; BibTeX for bib; PDF-on-disk + stderr summary for fetch; a --dry-run JSON plan in the dry-run variants) is fixed by the subcommand and may vary across flags. Consult examples for the per-flag stdout form rather than assuming JSON.

Supported

Under --mode json the command emits a structured JSON body on stdout; otherwise the human form (e.g. info, list-recent, audit-log, provenance migrate, batch).

Trait Implementations

impl Debug for JsonMode

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Serialize for JsonMode

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.