Very good post on everything that’s wrong with Swagger (by @barraganc): blog.novatec-gmbh.de/the-pro…

Apr 4, 2017 · 1:08 PM UTC

15
165
14
230
Replying to @stilkov @hunt3ri @martinfowler @barraganc
I’ll remove this as I might have misunderstood your grammar.
Replying to @stilkov @ploeh @barraganc
I have never seen a good example of how hypermedia can be used without an interactive client. How do u get a server to interpret links?
2
You code it against the link context. No magic, just one extra level of indirection.
1
2
more replies
Replying to @stilkov
@dret @barraganc As often is the case, you want something done well, you do it yourself. Problem is, nobody wants to. Not anymore.
Replying to @stilkov @barraganc
Brings back painful memories of JAX-RPC/wscompile brittle clients. Auto-generated clients suck.
1
Replying to @stilkov @barraganc
have you taken a look a Spring REST Docs? Different set of tradeoffs you might appreciate.
2
1
Replying to @stilkov @barraganc
I agree about code generation issues. But the author should have looked up OpenAPI 3.0.0 before stating about lack of hypermedia support.
Replying to @stilkov @martinfowler @barraganc
Had good experience of Swagger. Very good for discussing and agreeing API contracts. Never used the codegen and it is not mandatory.
1
Replying to @stilkov @barraganc
Someone send a PR to fix the enum behaviour please. (seems like an easy fix and not a fundamental problem in swagger)
Replying to @stilkov
@barraganc if you say "API first" and then use Java annotations that sounds pretty much like "code first" ;-)
1
Load more