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
Optimise human readable output for narrow terminals #85
Comments
Re-opening as #87 was a partial fix/mitigation. |
Thanks for trying osv-scanner and opening this issue! We've made some changes to mitigate this, and released https://github.com/google/osv-scanner/releases/tag/v1.0.2 which includes:
Most of our team is out for the rest of the year, but once we're back early next year we'll work on improving this further! |
Thanks ! |
@oliverchang @another-rex this could be a good time to talk about supporting the output style of
what do you think? |
I do like how that looks, we can add a flag like e.g. |
I believe there's no more remaining work here? (@another-rex please reopen if I'm wrong). |
When using the default textual output and the SOURCE path is long enough, the output is truncated.
All lines end with a
≈
and are truncated which make the output unusable because it misses the OSV URL entirely.I know about the JSON output, but I'd like to have an untruncated textual output too because it is more readable.
The text was updated successfully, but these errors were encountered: