Re:Swagger is now the OpenAPI Specification
by AdeptusAquinas on Monday October 23, 2017 @02:07PM
(#15535427)
I would assume most people would use an extension to generate swagger off their endpoints on demand. Thats what I do in ASP.NET, via a library called Swashbuckle: Swagger and Swagger UI in three lines of code.
[ Parent
| on HN ]
Re:Swagger is now the OpenAPI Specification
by mmsmatt on Monday October 23, 2017 @03:10PM
(#15536042)
SOAP, WCF, CXF, et al, what’s old is new again.
It’s strange to have been playing this game long enough to see a full cycle.
Here be dragons.
Re:Swagger is now the OpenAPI Specification
by AdeptusAquinas on Monday October 23, 2017 @03:44PM
(#15536337)
Biggest difference continues to be the complexity of the client required. For HTTP webservices, its still a massive step forward.
Re:Swagger is now the OpenAPI Specification
by avita1 on Monday October 23, 2017 @04:45PM
(#15536796)
What does the complexity matter? Either way you're running some service description file through some build tooling to generate some human unfriendly code. Who cares how big or complex the code in the middle is?
Re:Swagger is now the OpenAPI Specification
by AdeptusAquinas on Monday October 23, 2017 @05:45PM
(#15537186)
Because in most cases that I have experienced, no, you are not running the sdl through a generator to create a client. You are instead instantiating a http client, setting the right headers, urls, package bodies etc, all by hand. Something which is done in lieu of using a code generator because its trivial with an HTTP web service.
Furthermore, with an http api and depending on your security model, you can test/inspect a good portion of your APIs directly with a browser - a zero-cost client for all http apis that you get for free.