-
Notifications
You must be signed in to change notification settings - Fork 120
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
Add JSON output option #152
Comments
Two comments: GitI don't think we should copy Git naming for these options... Git is not the software I would use as a UX example... we get used to it, but it's not intuitive. It's my own opinion and I use it almost since it exists... Output formatif we output a machine readable format, why not just an already established format? I suggest outputing JSON directly as you can handle it in most languages, and even using shell scripts See for instance what Heroku app does: https://devcenter.heroku.com/articles/heroku-cli-commands This is something explained also in https://clig.dev/#output and I think we should follow these guidelines:
|
|
Need the feature for large document repository. JSON is pretty,current output format hard to parse using simple grep/sed/awk skills. The following shell would extract 404 errors, but not precisely get the result I need: sed -n '/^FILE: /,/[✖]/p' /path/to/deadlink-output.log |
Depends on
Proposal
Add a new flag (ex.
--porcelain
; like in git) that will result in easy to parse output.Reason
It's quite to parse any output from this amazing tool
Suggested output format
Example Output
Details
The text was updated successfully, but these errors were encountered: