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.
-
|
Hi Jan, thank you for your reply!
However, do correct me if I am wrong, but it seems to me that this empty list can only be added manually as you have mentioned in your second reply, yes? This is also to say if we were to add the dependencies using the library's Thank you! |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
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
refvalue, without thedependsOnkey 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