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

Need Human-readable output for get-nodes #26

Open
dopheide-esnet opened this issue Oct 20, 2022 · 1 comment
Open

Need Human-readable output for get-nodes #26

dopheide-esnet opened this issue Oct 20, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@dopheide-esnet
Copy link
Contributor

I've been playing around with a human-readable table for get-nodes. I've got working code as an example, but I feel like we can wait a bit to see what other output commands we may want to support.

dopheide-esnet@858e06c

@ckreibich ckreibich added the enhancement New feature or request label Oct 22, 2022
@ckreibich
Copy link
Member

Yeah this is great, thank you for exploring — I fully agree we don't want the JSON output as the default thing to consume by humans. The only question is how to structure/standardize its processing.

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

2 participants