Simplify safe YAML conversion into shared report values

This commit is contained in:
2026-11-07 00:32:51 +00:00
parent 647a9d5372
commit e7b00efc07
2 changed files with 55 additions and 30 deletions

View File

@@ -168,11 +168,13 @@ and universal format availability. Explicit operator selection wins; otherwise
core selects text for a supplied template or chooses from the logical report
shape. Command-specific format defaults are omitted from the initial API.
Plain text, YAML, and JSON land together. The roadmap selects standard Go JSON
serialization conventions for core-serialized report values, with separate core
adaptation for native configuration YAML. Text templates use Go's `text/template`
serialization conventions for core-serialized report values. Core explicitly
converts safe inspection YAML into ordinary report values, preserving data
meaning and redaction without a separate native-YAML preservation path.
Text templates use Go's `text/template`
with the original Go report value. Without a template, structured text output
reuses the YAML renderer; template errors never trigger fallback. Native-document
decisions remain there. XML is removed from current consideration.
reuses the YAML renderer; template errors never trigger fallback. Multiple-result
framing remains open there. XML is removed from current consideration.
Markdown and other potential formats are not selected for this adoption; new
core formats will work with
existing commands without per-command adoption.