Use a scope-keyed mapping for aggregate configuration reports
This commit is contained in:
@@ -173,8 +173,10 @@ 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. Multiple-result
|
||||
framing remains open there. XML is removed from current consideration.
|
||||
reuses the YAML renderer; template errors never trigger fallback. Aggregate
|
||||
configuration display uses an ordinary scope-keyed mapping through the same
|
||||
renderers, with no scope-order guarantee or separate-document machinery.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user