Context
CLIs that produce machine-readable output are far more useful in scripts and CI pipelines. Adding a global --json flag lets users pipe w3-kit output into jq, other tools, or test harnesses without scraping text.
What to build
Implement a global --json flag that, when set, causes all read commands (e.g., chains list, chains show, future tokens list, etc.) to print structured JSON instead of human-formatted text. Write commands (scaffolding) are out of scope for this issue.
Acceptance criteria
Pointers
- Pairs well with the future
chains and tokens commands
- Reference: GitHub CLI (
gh) uses --json field selection — start with simple full-payload JSON, field selection can be a follow-up
Complexity
🟡 Intermediate
Context
CLIs that produce machine-readable output are far more useful in scripts and CI pipelines. Adding a global
--jsonflag lets users pipew3-kitoutput intojq, other tools, or test harnesses without scraping text.What to build
Implement a global
--jsonflag that, when set, causes all read commands (e.g.,chains list,chains show, futuretokens list, etc.) to print structured JSON instead of human-formatted text. Write commands (scaffolding) are out of scope for this issue.Acceptance criteria
--jsonflag works on every existing read command--jsonis set also produce JSON (e.g.,{ "error": "..." }) and exit with a non-zero code--helpPointers
chainsandtokenscommandsgh) uses--jsonfield selection — start with simple full-payload JSON, field selection can be a follow-upComplexity
🟡 Intermediate