2 to 3 migration guide

[ritch]

Hello OpenAPI compadres. I wanted to see if anyone out there is working on a migration guide for the 3.0 spec. I'm not sure if now is the right time for such a thing, but its becoming something I'm very interested in and wanted to perhaps kick off the effort if no one else has.

Any info/links would be very helpful :).

[ritch]

@fehguy @webron ^^^

[fehguy]

Yes--it'll be coming after the preview for the 3.0 spec at the end of Feb.

[ritch]

@fehguy want any help with it?

[fehguy]

Is rice white? Yes please! Please follow announcements and would love participation in this. We will document structural transformations and also be building OSS tools to do so.

[MikeRalphson]

I'm working on a Node.js based converter/validator from Swagger 2.0 to OpenAPI 3.0.0 (RC0) here, it will at first only aim to convert self-contained definitions.

It's very much a WIP until the 3.0.0-RC0 examples and schemas are published.

It is tested against APIs.guru, SOM Hapi and this collection, but I would gladly hear of other test corpuses.

Please feel free to add other tools/resources as they come along to this unofficial list.

[mission-liao]

I've written a python client in python (pyswagger), which can also be used to convert documents from Swagger 1.2 to 2.0. The conversion from 2.0 to 3.0 is also planned and ongoing.

[MikeRalphson]

Google have a draft schema for OpenAPI 3.0.x, it contains a few mistakes but would be an excellent starting point for an official schema - except if the official schema is going to be in JSON schema Draft 5 not Draft 4?, /cc @timburks

[timburks]

@MikeRalphson I'm happy to fix any problems in our draft schema.

Please post issues here or send them to me directly and I'll post and respond to them.

[jpuck]

Now that 3.0 has been released, can someone point me to the 2.0 -> 3.0 migration guide? 🙏 Thanks

[MikeRalphson]

I don't think anything official has been published yet, but swaggerhub has an integrated converter / validator and there are OSS alternatives - associated blog post.

[MikeRalphson]

Closing due to inactivity - there are several resources on migration from OAS 2.0 to 3.0 available.