v0.10.0 #500
Merged
v0.10.0 #500
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
used further up in the stack for documentation management.
it has been sat there doing nothing, now it’s wired up, fixed tests and fixed function name mappings in preparation for the doctor.
They were all kinds of out of whack!
if unsupported properties are submitted, validation will fail for rules
would have broken non openapi specs.
updated function names in schema tests
breaks too much
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.
Quality / Stability release
This is a breaking change for consumers of vacuum as an API. It introduces some changes to the
Schemaof all built in rule functions. These changes are required to correct some broken behavior when using vacuum as an engine for other tools.A number of built in rule functions have have schemas updated to be accurate.
A new
GetCategorymethod signature has been added to theRuleFunctioninterface, that requires all rule functions to expose the category the rule is apart of.severityis now a required property of all rule definitions.It addresses the following issues