Model Schemas

[ritch]

The explorer should use the model's schema.

Details TBD.

[AndrewMartens]

+1.

Doing a Loopback demo and would love to have the schema visible there, but for now I'll just hand-wave around it.

[STRML]

It seems the issue is that the models config is not being passed from app.docs() (loopback/lib/application.jsL239) to Swagger()(strong-remoting/ext/swagger.jsL14). I attempted to pass the model config into this object and place it into each apiDoc object but I'm afraid I don't know enough about the swagger spec to finish it. I hope this helps it along.

[adilwali]

Is there an edge version where this is fixed? (I just installed strong-cli and generated an app.)

I'm happy to help dig in and get it working. It would really help me pitch this to my team.

[bajtos]

The current version of loopback-explorer is based on swagger spec 1.1 which does not include type/model descriptors. The first step on the path to model descriptors is upgrading to swagger spec 1.2 - see the transition guide.

[bajtos]

See also #7, it requires upgrade to 1.2 too.

[raydemandforce]

Is there a time table to update to swagger spec 1.2?

[ritch]

@raydemandforce - it is not a high priority at the moment. If anyone is interested I can help them wrap their heads around what it would take to patch strong-remoting to support swagger 1.2.

[STRML]

@ritch Going to take a crack at it as we will be using the swagger docs as our public-facing API docs. Any pointers?

Also - how do you feel about moving to the swagger-node-express generator for creating the Swagger JSON? I could write an adapter library so we can benefit from Wordnik's updates as 2.0 and further versions are introduced.

Additionally we could be using swagger-ui as a dependency so changes to the static HTML/JS/CSS don't need to be pulled in manually.

[STRML]

This can be closed, fixed by #14.

[bajtos]

The feature is available as of v1.2.0.