channel list: support --format yaml (parity with read) #2

Closed
opened 2026-06-02 22:43:23 +00:00 by coilysiren · 1 comment
Owner

o2r channel list --format yaml was rejected:

o2r channel list --all --format yaml
o2r: channel list: --format must be table or json, got "yaml"

Inconsistent with o2r channel read, which supports json|yaml|markdown. The list endpoint (GET /agent-channel) does no server-side format negotiation (only the single-channel view does), so yaml is rendered client-side via yaml.v3. markdown stays read-only since it is the single-channel onboarding render, not a collection view.

Fix: list now accepts --format table|json|yaml.

`o2r channel list --format yaml` was rejected: ``` o2r channel list --all --format yaml o2r: channel list: --format must be table or json, got "yaml" ``` Inconsistent with `o2r channel read`, which supports `json|yaml|markdown`. The list endpoint (`GET /agent-channel`) does no server-side format negotiation (only the single-channel view does), so yaml is rendered client-side via yaml.v3. markdown stays read-only since it is the single-channel onboarding render, not a collection view. Fix: `list` now accepts `--format table|json|yaml`.
coilysiren referenced this issue from a commit 2026-06-02 22:43:42 +00:00
Author
Owner

Fixed in v0.1.2 (commit 126b868). o2r channel list --format yaml renders block YAML client-side; verified live on the installed binary.

Fixed in v0.1.2 (commit 126b868). `o2r channel list --format yaml` renders block YAML client-side; verified live on the installed binary.
Commenting is not possible because the repository is archived.
No description provided.