Problem
CLI commands like list feeds and list entries output plain text, making it difficult to parse results in scripts or pipe to other tools.
Proposed Solution
Add a --json flag to the list subcommands that outputs structured JSON (one JSON object per line for easy streaming/processing).
Use Case
Users building automation scripts can easily parse feed/entry data with tools like jq or in any programming language. For example:
reader list feeds --json | jq '.url'
reader list entries --json | jq -r '"\(.feed_url) \(.title)"'
This would enable better integration with monitoring tools, custom dashboards, and CI/CD pipelines.
Problem
CLI commands like
list feedsandlist entriesoutput plain text, making it difficult to parse results in scripts or pipe to other tools.Proposed Solution
Add a
--jsonflag to thelistsubcommands that outputs structured JSON (one JSON object per line for easy streaming/processing).Use Case
Users building automation scripts can easily parse feed/entry data with tools like
jqor in any programming language. For example:This would enable better integration with monitoring tools, custom dashboards, and CI/CD pipelines.