-
Notifications
You must be signed in to change notification settings - Fork 42
Fix json schema example #684
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
Conversation
…icense wording, and format blank lines around header docstrings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem right. Why would Exploitation have a key of "V"? "V" used to be Virulence, which was replaced by "Automatable" ("A"). So this change to "Exploitation" seems out of place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for catching that I went to L34 instead of L54. Update incoming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thes scheme example should go in an archive folder, we no longer support this format
data/schema_examples/Computed-CVE-2014-0751-Coordinator-with-tree.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spawned @sei-vsarvepalli 's comment into a new issue #687 so we don't have to hold this PR for merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahouseholder
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Will merge shortly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spawned @sei-vsarvepalli 's comment into a new issue #687 so we don't have to hold this PR for merging
Uh oh!
There was an error while loading. Please reload this page.