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
Refactor Checks to Operate on the Context Object #714
Comments
Startedon branch |
NoUnusedDefinitionsCheckI wanted to create a PR for a 2nd rule today, but that did not happen. I am stuck with one case that fails and need to figure it out. The branch in GIT is: Next steps
|
Intrigued to notice "SecureAllEndpointsWithScopesRule (currently not used in production)"... is there an issue raised with known problems for this rule? Seems a shame that the two Zally installations I know of (yours and mine) currently both disable this rule! |
…ect to support OpenAPI 3 (#714)
…ext object to support OpenAPI 3 (#714)
… object to support OpenAPI 3 (#714)
…ect to support OpenAPI 3 (#714)
…itions-via-json feat(server): NoUnusedDefinitionsRule reimplemented checks JsonNode
After implementing the initial support for OpenAPI3 we have to adjust the check implementations. Instead of operating on the Swagger object, the checks have to use the
Context
object. Doing this, the checks become universal - applicable against Swagger2 and OpenAPI3 specifications.Acceptance Criteria:
Context
objectList of Rules to be refactored
Zalando (API Guidelines)
Done
High priority list (please migrate these first)
Lower priority list
Nic-to-have, less important checks will be refactored as part of #834
The text was updated successfully, but these errors were encountered: