Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inference preferable format based on the situation #178

Open
StoneDot opened this issue Sep 30, 2023 · 0 comments
Open

Inference preferable format based on the situation #178

StoneDot opened this issue Sep 30, 2023 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@StoneDot
Copy link
Contributor

This proposal is related to #176.

As I mentioned in #176, the dynein format is preferable when showing output for human reading, but JSON is more suitable for reading by programs. I propose inferring the preferred format using atty.

If the user uses a pipe, a program consumes output; if the user does not, it means that a human checks the output. I think this correspondence can be used to infer a preferable format.

@StoneDot StoneDot added this to the v0.4.0 milestone Sep 30, 2023
@StoneDot StoneDot added the enhancement New feature or request label Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant