This is a totally out there, left-field, but kind of interesting to think about. I can certainly understand why you might not want to support this, but give it some thought.
It would be totally amazing if there were some way to pull in type definitions / annotations by a Swagger API url. In the most general sense, other urls that return JSON that could be coerced into a type definition would be similarly convenient, but Swagger lays down a framework for simple type discovery. In essence, we're talking about a simple DTO with some properties
We use Swagger to generate API docs for our JSON-based REST services. It would be quite fantastic if we could in some way annotate objects with Swagger API urls, to get autocomplete over these objects as well.
This is a totally out there, left-field, but kind of interesting to think about. I can certainly understand why you might not want to support this, but give it some thought.
It would be totally amazing if there were some way to pull in type definitions / annotations by a Swagger API url. In the most general sense, other urls that return JSON that could be coerced into a type definition would be similarly convenient, but Swagger lays down a framework for simple type discovery. In essence, we're talking about a simple DTO with some properties
We use Swagger to generate API docs for our JSON-based REST services. It would be quite fantastic if we could in some way annotate objects with Swagger API urls, to get autocomplete over these objects as well.
Here's a related article you might find useful http://www.apievangelist.com/2013/03/21/interactive-api-documentation-with-swagger/