OpenApi v3 Spec

Issue #64 resolved
Marcel Overdijk created an issue

Are there any plans for supporting OpenApi v3 Spec files?

Comments (15)

  1. James Navin

    There is, yes, but probably not for another month or so (its going to be hard for me to find the time before then).

  2. Marcel Overdijk reporter

    OK thx for your response. This issue can be use to track the progress. With the new Link object in the v3 spec it will be easier to document HATEOAS api's, and of course test if the actual responses follow the spec :-)

  3. Robert Massaioli

    It seems that OpenApi v3 now supports 'anyOf'. We are likely to need this support for the tool we are writing @jfnavin .

  4. James Navin

    For basic support:

    1. Evaluate maturity of the v3 parser lib
    2. Bump to new version of parser lib
    3. Fix broken API usage
    4. Add tests for v3 specs
    5. Do a major-version release

    We would then need to identify new functionality in v3 and raise tickets to add coverage for those features (anyOf, Link etc)

  5. James Navin

    @dexwest - is your team using OAI v3 in production yet? Ive been keeping an eye on the Java tooling and AFAIK its still not out of release candidate status. I haven't invested any time in supporting v3 as of yet as I assume most users are still on v2 (and there are enough bugs/feature requests in the current version of the SRV to keep me busy 😃 )

  6. John Thompson

    @jfnavin - is there a timeline for OAI v3 support? I'm documenting some public facing Spring Boot services and need to decide between using v2 or v3.

  7. James Navin

    @johnthompson - I don't have a timeline at the moment (unfortunately I only get time to work on this library a few days a month). I did see that a final 2.0.0 release of the v3 swagger-parser lib has been released so I might try and spike out a branch soon to get an idea of how much effort is required to add support.

  8. James Navin

    I have started work on adding support for the OpenAPI v3 spec.

    There is a new v2.0 branch that contains the initial work in anticipation of a major version release.

    Current state is:

    • Existing test suite (based on v2 specs) passes (with some caveats...)
    • Validation of form data is not yet supported
    • No support of features above what exist in the v2 spec

    I intend to add tests powered by v3 specs to confirm basic validation behavior, then look at adding support for new v3 features.

    My likely plan of attack will be:

    1. General refactoring and cleanup of existing codebase
    2. 'fill the gaps' where the v3 spec has enhanced what the v2 spec already supported (e.g. discriminator mappings etc)
    3. Identify 'critical' new functionality to add validation for
    4. Release 2.0
    5. Add validation for 'non-critical' pieces as part of regular development/maintenance

    Progress on the v2.0 release is tracked in #113. Suggestions / comments welcomed there.

  9. James Navin

    swagger-request-validator 2.0.0-rc3 has been released. This will likely be the final RC before the 2.0 final.

  10. Log in to comment