feat: add JSON Schema to JSON output #80
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Addresses Issue #79 |
nscuro
reviewed
Mar 2, 2023
There was a problem hiding this comment.
Thanks @mcombuechen!
There's an additional area where the JSON schema needs to be set, namely when converting between schema versions:
Lines 79 to 80 in 39a1d8f
Signed-off-by: Maximilian Combüchen <[email protected]>
|
@nscuro made the change to the |
nscuro
approved these changes
Mar 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a
$schemafield to the JSON output, to achieve parity with the CycloneDX JavaScript library. The value points to the JSON schema definition file at cyclonedx.org.