Replies: 2 comments 1 reply
-
First off, why would it be important that the optional per schema, these both are equal: {
// ...
"dependencies": [
{
"ref": "foo"
}
// ...
]
// ...
} {
// ...
"dependencies": [
{
"ref": "foo",
"dependsOn": []
}
// ...
]
// ...
} |
Beta Was this translation helpful? Give feedback.
-
the sample above was human generated. read https://github.com/CycloneDX/cyclonedx-python-lib/blob/8f81322ebdb6614569ab9301a76f7354fdd0051b/tests/_data/schemaTestData/README.md the file resides in this repo to test whether the libraries own schema validator is working as expected. |
Beta Was this translation helpful? Give feedback.
-
Hello, thank you for creating this library, it is a super helpful and essential tool for us! :D
I do have a question though, when generating a sample CycloneDX file from the complex.py example, the components that doesn't have any more dependencies just return with the corresponding
ref
value, without thedependsOn
key at all, unlike as shown here in the valid dependency sample JSON file.I was wondering how can I ensure that the components with no further dependencies be generated such that it complies to the sample file shown above?
Any help is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions