1

How the fuck you can fucked up a Restful api backend built on SWAGGER!

Comments
  • 0
    Tell us.
  • 2
    Swagger is just a tool. It's easy to fuck it up.
  • 1
    Swagger is just documentation, right? 🤔
  • 1
    By manually updating swagger. Or, more to the point, failing to manually update swagger.
  • 1
    @olback
    The ideal flow for swagger/raml/etc is you design your API in it, code gen the interfaces and validate endpoints against it programmatically.
  • 0
  • 0
    I wonder how one can break it BECAUSE of Swagger? 🤔😂
  • 0
    @SortOfTested except the code generator doesn't work because the OpenSSL binding of a dependency of another dependency of yet another dependency is outdated and consequently doesn't support your OpenSSL version. Other than that: It simply generates invalid code.

    My experience with several swagger code generators in a nutshell.
  • 0
    @PublicByte
    The code gen should generate interfaces. It's up to you to actually implement endpoints.
  • 0
    @SortOfTested well that's obvious. I'm talking about generating invalid bootstrap code which shouldn't be changed.
  • 0
    I had to fix the bootstrap code before the compiler complained about the OpenSSL bindings part 😂
  • 0
    @PublicByte
    Are you talking about swagger UI? I get the impression were talking different things. Openssl has no part in the code gen for services.
  • 0
    @SortOfTested the OpenAPI rust code generator (rust-server) uses OpenSSL bindings. ¯\_(ツ)_/¯
  • 0
    @PublicByte
    Seems like it's overreaching. The spring and .net ones just produce interface code classes.
Add Comment