Hi Dan,

 

Putting aside semantics, OAS3 is the latest and newest version of the 
specification. Many users have waited for it, and we want people to be aware of 
it, educate themselves on it and understand how they could benefit from it.

 

As to be expected, with any new version of a specification, tooling takes time 
to catch up. At the moment, we have support for OAS3 in the editor and the UI, 
with some of Java projects coming out this week.

 

The codegen, being based on a bunch of other Swagger projects, will take time 
to pick up the changes, but it’s definitely in the plans.

 

SwaggerHub never announced support for OAS3 yet, much like most of our OSS 
tools. SNAPSHOTS, as you know, allow users to test pre-releases which helps US 
to provide YOU with better final product.

 

We’re going to be updating on the progress of OAS3 support in our blogs and 
twitter accounts.

 

I take the criticism regarding finding the 2.0 specification though – for now 
we’ve added a simple link to it from the specification page, and we’ll work on 
making it clearer in the upcoming days.

 

From: <[email protected]> on behalf of Dan Rumney 
<[email protected]>
Reply-To: "[email protected]" 
<[email protected]>
Date: Tuesday, August 15, 2017 at 12:54
To: Swagger <[email protected]>
Subject: Why is OpenAPI front and center on the site when none of the tools 
support it?

 

Am I missing something here? 

 

The swagger site pushes v3.0.0 as the de facto standard. It's what you see when 
you view the "Specification"... you have to dig for v2.

 

The problem is, nothing in the swagger ecosystem seems to be quite v3 ready. 
The Open Editor supports it (at least, in terms of validation), but the 
generated documentation is full

of bugs. SwaggerHub can't handle v3. I get NullPointerExceptions when I try to 
use the 3.0-SNAPSHOT of swagger-codegen... hell OpenAPI support is only 
available in a snapshot... there isn't even a reasonably stable download.

 

So... I ask: am I missing something? Is 3.0.0 ready for the field, or not? If 
so, where is the tooling? If not, why is it pushed as the specification?

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to