We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While indented JSON output is great for a human, for script-based use a more compact JSON output would generally be better.
For example, asking for --indent the output would be nicely formatted JSON (like before):
--indent
$ spdx --indent "GPL-3.0" # => { # "expression": { # "license": "GPL-3.0-only" # }, # "errors": [] # }
...but when asking for --compact output, the JSON would exclude any non-meaningful whitespace for a compact, single-line output.
--compact
$ spdx --compact "GPL-3.0" # => {"expression":{"license":"GPL-3.0-only"},"errors":[]}
For backward compatibility, it'd be better to default to --indent to not break any existing usage.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While indented JSON output is great for a human, for script-based use a more compact JSON output would generally be better.
For example, asking for
--indent
the output would be nicely formatted JSON (like before):...but when asking for
--compact
output, the JSON would exclude any non-meaningful whitespace for a compact, single-line output.For backward compatibility, it'd be better to default to
--indent
to not break any existing usage.The text was updated successfully, but these errors were encountered: