Skip to content

Parse invalid/incomplete OpenAPI specs #904

@guites

Description

@guites

We need to discuss ways to allow users to convert non compliant OpenAPI specs into valid ScanAPI files. This is mostly because a lot of OpenAPI spec generation tools create files that are not 100% compliant, with some generating additional fields, skipping required fields, etc.

Context: #866 (comment)

Metadata

Metadata

Assignees

No one assigned
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions