Structured data as JSON or YAML

Many Console fields hold structured data — a nested object of keys, values, lists and maps. Examples are an execution's output_value and input_value, a setting's value, the JSON attributes of a custom object, and the configuration of connectors, schedules, dashboards and schemas.

These fields render structured data as YAML by default. A toolbar control on each structured-data field switches the representation between YAML and JSON.

The toggle

Every structured-data field shows a button on its editor toolbar labelled "Structured data shown as YAML — click to switch to JSON" (and, once switched, the mirror label for switching back to YAML). Clicking it re-renders the field's value in the chosen representation, with syntax highlighting and pretty indentation.

The choice is a single per-user preference. It is remembered across page reloads, and it applies to every structured-data field at once: switching one field to JSON shows all of them as JSON until you switch back. This lets you read and edit structured data in whichever representation you prefer throughout the Console.

Read-only fields

On read-only fields — such as an execution's output_value — the toggle controls the display only. The value converts between pretty YAML and pretty JSON for reading; nothing is written back. Dashboard widgets that show an execution's output follow the same per-user preference.

Editable fields

On editable fields the two representations are exclusive: while a field is shown as YAML it accepts YAML, and while it is shown as JSON it accepts JSON. Because JSON is a subset of YAML, switching representation converts the current text to the pretty form of the target representation without changing the underlying value — it is stored identically regardless of which representation you edit in, and switching representation by itself does not mark the form as changed.