Hi,
I am using the maillist as there is no way to register on the git page to open an issue.
The current JSON api (for example https://api.reuse.software/status/github.com/erooster-mail/erooster.json ) includes the spdx output and the lint output as verbatism in text form. This in my opinion is not really in any way machine readable at this time. The spdx I guess is fine considering it's a standard in itself. However the lint output seems weird to me.
Is there any reason why the values are not included as keys? Whats the reasoning to only include the data as markdown?
---
Marcel Radzio
Hi Marcel,
On 28.10.2023 15:50, Marcel Radzio wrote:
The current JSON api (for example https://api.reuse.software/status/github.com/erooster-mail/erooster.json ) includes the spdx output and the lint output as verbatism in text form. This in my opinion is not really in any way machine readable at this time. The spdx I guess is fine considering it's a standard in itself. However the lint output seems weird to me.
Is there any reason why the values are not included as keys? Whats the reasoning to only include the data as markdown?
There is no specific reason, just a missing feature. `reuse lint --json` is a relatively new feature and the API hasn't been modified to support it yet. However, it shouldn't be too hard to implement it, the foundation exists already.
I have created an issue for this: https://git.fsfe.org/reuse/api/issues/85
Best, Max
Ah ok :) Thanks for the reply and opening the issue!
On 03.11.23 13:36, Max Mehl wrote:
Hi Marcel,
On 28.10.2023 15:50, Marcel Radzio wrote:
The current JSON api (for example https://api.reuse.software/status/github.com/erooster-mail/erooster.json ) includes the spdx output and the lint output as verbatism in text form. This in my opinion is not really in any way machine readable at this time. The spdx I guess is fine considering it's a standard in itself. However the lint output seems weird to me.
Is there any reason why the values are not included as keys? Whats the reasoning to only include the data as markdown?
There is no specific reason, just a missing feature. `reuse lint --json` is a relatively new feature and the API hasn't been modified to support it yet. However, it shouldn't be too hard to implement it, the foundation exists already.
I have created an issue for this: https://git.fsfe.org/reuse/api/issues/85
Best, Max _______________________________________________ REUSE mailing list REUSE@lists.fsfe.org https://lists.fsfe.org/mailman/listinfo/reuse
This mailing list is covered by the FSFE's Code of Conduct. All participants are kindly asked to be excellent to each other: https://fsfe.org/about/codeofconduct