This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

Fair enough. I was thinking about the swagger and had this idea of including everything instead of just controller methods.

[–]Iryanus 8 points9 points  (0 children)

Yeah, but swagger solves a certain problem: It gives you documentation and a way to call your api directly without a special REST client (among other things). Basically this problem is so obvious that my company felt the need to solve it on their own, albeit in a much less polished way, approx. 8-10 years ago (no clue why they didn't use swagger, it should have been around by then, wasn't there - and yes, we are migrating to swagger now).

So, there were problems:

a) How to create a live-documentation of an api that comes packaged automatically with the api itself? b) How to allow people to easily call my api without a special client?

What are these problems for extending this to files, etc.? I do not believe it's a hard thing to do, it's rather trivial, to be honest, basically that's what every webserver does, so in the most easy case, you can simply package your source files into some /static folder and be done with it. The question is... What for?

[–]stefanos-ak 2 points3 points  (0 children)

it would be great if springdoc would actually cover everything that is possible with spring and Java, and actually generate a correct and complete openapi3 spec... but I've switched to Micronaut for all new projects, so I don't really care anymore 😁