Adopt JSON conventions for shared report representation
This commit is contained in:
@@ -167,8 +167,10 @@ content selection, core-owned rendering, a text fallback with optional templates
|
||||
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; representation, template, and
|
||||
native-document details remain there. XML is removed from current consideration.
|
||||
Plain text, YAML, and JSON land together. The roadmap selects standard Go JSON
|
||||
serialization conventions for ordinary report values, with separate core
|
||||
adaptation for native configuration YAML. Text-template and native-document
|
||||
decisions remain 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.
|
||||
|
||||
Reference in New Issue
Block a user