-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rewrite CodeTF spec using JSON Schema #20
Conversation
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.
Thanks for doing this. I checked the schema against some CodeTF results I got from the orchestrator and found that it didn't match.
To catch cases where we accidentally make a breaking change to the schema, can we include an example of a valid CodeTF file and include a check in validate
that validates the schema against the example?
"type": "string", | ||
"description": "A longer description of the changes made" | ||
}, | ||
"detectionTool": { |
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.
The debate for this field properly belongs in #19. I'm happy to remove it here if we just want to move ahead with this change.
No description provided.