How do JSON result bodies become Swagger model documentation? about rho

[aryairani]

P.S. I am looking at the Swagger 2.0 definitions: and getting excited because they match what I want to start outputting.

[bryce-anderson]

No, the AutoSerializable trait isn't part of the swagger process. It is an experimental construct I made up to allow you to easily send case classes. I don't think it will ever escape the examples as it feels a little 'magic'. If it belongs anywhere permanently, it would be in http4s proper.

[aryairani]

No, ok. So AutoSerializable is just part of the way the example project produces the response body.

Then how does the example project's json become a swagger json definition?

[aryairani]

Basically, I want to understand how to start extending this capability. Complicating things a little bit is the fact that Swagger 2.0 is much more expressive, and I kind of want to jump onto that train, although it is in motion. (Edit: Or is it?)

[bryce-anderson]

The SwaggerSupport trait is tasked with maintaining and rendering the documentation here in master and here in the swagger2.0 branch. @cencarnacion has submitted an excellent PR concerning swagger 2.0 which I hope to merge in the very near future, so its probably worth looking at that code from now on.

[aryairani]

Ok, I see it, and in particular I'm looking at org.http4s.rho.swagger.TypeBuilder currently.