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

discuss supporting other reuse lint report output formats (exporters) #676

Closed
kbroch-rivosinc opened this issue Feb 9, 2023 · 4 comments
Labels
enhancement New feature or request priority/low Low priority

Comments

@kbroch-rivosinc
Copy link
Contributor

Related to #672

Currently it looks like the report output is in markdown.

IMO it would be useful to provide other formats. Bandit has a comprehensive list.

Here's a subset I'd be interested in:

  • xml (specifically junit test format)
    • why: for existing projects trying to get REUSE compliant may be a journey, this would facilitate eventual compliance by monitoring progress over time (ex: using in gitlab)
  • html
    • why: then don't have to pipe existing md output into another tool to generate it

I realize xml format might have the same response as here: #655 (comment) but just wanted to pose the use case.

@carmenbianca
Copy link
Member

See also #654 #183

XML (junit test) sounds interesting. I'm not sure we're going to take initiative on that, though. JSON has higher priority for us at the moment.

Thanks for the issue!

@carmenbianca carmenbianca added enhancement New feature or request priority/low Low priority labels Feb 9, 2023
@kbroch-rivosinc
Copy link
Contributor Author

Thanks for --json issue links (I missed those). I'll check back in after --json PR lands. I bet I can transform that output to my needs.

@mxmehl
Copy link
Member

mxmehl commented Feb 10, 2023

See #320 for the junit.xml request.

Could we close this issue as there are already issues/PRs for JSON and junit?

@kbroch-rivosinc
Copy link
Contributor Author

Closing this issue is fine with me.

@mxmehl mxmehl closed this as not planned Won't fix, can't repro, duplicate, stale Feb 10, 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 priority/low Low priority
Projects
None yet
Development

No branches or pull requests

3 participants