fix: use markdown key-value tables for view commands instead of JSON code fences #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-1-print-json-to-markdown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Fixes #1 — all
viewcommands now render human-readable markdown key-value tables by default, instead of JSON wrapped in code fences. The--jsonflag still outputs the full API JSON response.Changes
Core (
src/output.rs)DetailRowstruct (key-value pair withTabled+Serialize)print_detail()method — renders markdown table (default) or JSON (--json)Fixed commands (12 files)
issue viewpr viewcomment viewreview viewnotification viewuser viewrelease viewrelease attachment viewissue-attachment viewcomment-attachment viewbranch-protection viewworkflow viewBefore / After
Before:
After:
Notes
print_json— these are lower priority for markdown rendering since they show confirmation output--jsonoutput is unchanged (full API JSON)