Keep on the lookout for swagger-core 2.0 artifacts about rho

[arouel]

Great that Swagger 2.0 is out. If we upgrade as soon as possible we reduce the migration effort from 1.3.

Does Swagger 2.0 supports generic types natively, especially on arrays?

[bryce-anderson]

Update
The spec is now available here. I'm not 100% certain, but the swagger UI components here don't appear to be complete.
The model appears to be dramatically better than 1.2, so as soon as the swagger UI works, I want to migrate.

[bryce-anderson]

Update

The java swagger implementation is coming along slowly here and its looking like there won't be a scala specific version. Perhaps that for the best as it may be a bit more difficult to implement using the java api, but it should be more stable.

[arouel]

We could ask @casualjim if he plans to upgrade swagger-scala to version 2.0, right?

[bryce-anderson]

In the second link (and his post may no longer be accurate) @casualjim states that its unlikely there will be a scala specific version.

[arouel]

Sorry, have mentioned it too late. Why would we need the Java-based Swagger API and could swagger-core be enough for our purpose?

[bryce-anderson]

Sorry, I didn't describe the situation clearly. When I said we should use the java-api, I mean't swagger-core, which is written in java.

[arouel]

Okay, thank you for clarifying it.

[bryce-anderson]

I tested the latest master of swagger-ui (its pretty easy, just clone the repo and point yourself to the dist/index.html for a working swagger-ui) and it appears that 2.0 is working enough to consider migrating. The only waiting piece is now swagger-core, which may actually be usable, I just don't know.

[bryce-anderson]

Artifacts are out. I"m closing this and opening an 'upgrade to swagger-2.0' issue.