v0.7.0 #408
Merged
v0.7.0 #408
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
everything needs an update, starting with the most noisy. Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
corrected some errors and cleaned things up in general, without changing any of the logic / outcomes. Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
a simpler design, better DX. Signed-off-by: quobix <[email protected]>
Finally, it’s time. After all this time - I can rebuild the way it was supposed to be. Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
…403 Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
stops confusion and completes Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Think your spec can pass it? Hah.. try it. Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
Signed-off-by: quobix <[email protected]>
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.
v0.7.0introduces a complete rebuild of the OWASP rule functions. They have now all been moved into custom functions. This was done because the previous rules were choking at scale, and all the paths were undecipherable.This update should address issue #398
view OWASP functions
Example functions re-written.
The examples functionality have all been rewritten. They now run much faster and are much more accurate. They have also been broken down into three rules, from the previous one.
Modified rule:
oas3-valid-schema-exampleThis rule now ONLY checks that schemas provided by examples are valid.
New rule:
oas3-missing-exampleview docs
This rule checks to ensure all Schemas, Parameters, Headers and Media Types have an
examplesorexamplefield set,and ensures that no empty values are provided.
New rule:
oas3-example-external-checkview docs
This rule checks that no examples in Parameters, Headers and Media Types have used both an
externalValueand avalueproperty.These modifications address #403 and #392
New feature 'Hard Mode'
All commands support the new
-z/--hard-modeflag. This will enable every built-in rule in vacuum. This is the highest level of compliance available built into vacuum.If you want to really test your OpenAPI spec, then try Hard Mode, and then feel sad.
Fixed
spectral-reportpathsIssues #295 and #304 have been addressed with the path cleanup work.
Dashboard and html-report updates
Only categories that triggered results are available in reports and the terminal UI now. #399