This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
(automatically) provide structured JSON outputs for commands when stdout isn't an ANSI-capable terminal #892
Labels
tooling
Tooling and developer experience improvements
What is your idea? Provide a use case.
Many (all?) commands return some fancy outputs which look (arguably) good in the terminal. While pretty, this isn't particularly useful for manipulating the output and building tools.
We could instead provide structured JSON outputs for a variety of commands (e.g.
aiken check
) ready for consumption.Why is it a good idea?
This enables more tools to rely on the CLI, and open up use cases for automation down the line.
What is the current alternative and why is it not good enough?
Current alternative requires awkward parsing of the output, which may contains color codes and whatnot.
The text was updated successfully, but these errors were encountered: