Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migrate checks to operate on the context object to support OpenAPI 3 (follow-up)

See original GitHub issue

Follow-up issue for #714.

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.

Most important rules have already been refactored in #714.

Acceptance Criteria:

The following checks are refactored to use the Context object
Minimal specifications are used in the tests

List of `Rules` to be refactored

SecureAllEndpointsWithScopesRule (currently not used in production) (PR)
ExtractBasePathRule (PR)
HyphenateHttpHeadersRule (Removed, see [discussion] (https://github.com/zalando/zally/issues/834#issuecomment-422937952)) (PR)
NoProtocolInHostRule (PR)
NoUnusedDefinitionsRule (PR)

Issue Analytics

State:
Created 5 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

1reaction

roxspringcommented, Sep 25, 2018

AvoidXZallyIgnoreRule operates on JsonNode not Swagger so I think can be considered done.
SecureAllEndpointsWithScopesRule already converted to Context

1reaction

vadegcommented, Sep 20, 2018

@maxim-tschumak I will take over in scope of PR for this ticket.

Top Results From Across the Web

OpenAPI Specification - Version 3.0.3 - Swagger

The OpenAPI Specification defines a standard interface to RESTful APIs which allows both humans and computers to understand service capabilities without ...

OpenAPI 3.1 - What's New and How to Migrate to/from Other ...

Announcing the migration support for OpenAPI 3.1. Learn what's new in the latest format and how to migrate to other API specification ...

Migrating to OAS 3.0 Using Swagger - YouTube

The OpenAPI Specification specifies the rules and syntax required to describe the API's interface. The OAS has evolved to meet the needs of ......

OpenAPI Specification v3.1.0 | Introduction, Definitions, & More

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover ...

Open API 3.0 support in Rational Software Architect Designer ...

Select OpenAPI Parameter or OpenAPI Response Parameter from OpenAPI3 palette. · While adding OpenAPI Parameter or OpenAPI Response Parameter to a Resource ...