Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. We're talking weeks or months of work done in seconds, wit...
Answer
#4: Post edited
by
Kevin Krumwiede
·
2024-01-08T19:58:29Z (10 months ago)
Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. We're talking weeks or months of work done in seconds, with greater reliability than a hand-coded client. Swagger is so valuable that if you don't publish Swagger docs for your API, you don't have a minimum viable product.- Also note that your title differs from your question body. Swagger docs and the Swagger UI are different things. My answer applies to your question body.
- Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. We're talking weeks or months of work done in seconds, with far less opportunity for human error than a hand-coded client. Swagger is so valuable that if you don't publish Swagger docs for your API, you don't have a minimum viable product.
- Also note that your title differs from your question body. Swagger docs and the Swagger UI are different things. My answer applies to your question body.
#3: Post edited
by
Kevin Krumwiede
·
2024-01-08T19:57:47Z (10 months ago)
Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. Swagger is so valuable that if you don't publish Swagger docs for your API, you don't have a minimum viable product.- Also note that your title differs from your question body. Swagger docs and the Swagger UI are different things. My answer applies to your question body.
- Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. We're talking weeks or months of work done in seconds, with greater reliability than a hand-coded client. Swagger is so valuable that if you don't publish Swagger docs for your API, you don't have a minimum viable product.
- Also note that your title differs from your question body. Swagger docs and the Swagger UI are different things. My answer applies to your question body.
#2: Post edited
by
Kevin Krumwiede
·
2024-01-08T19:55:47Z (10 months ago)
Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. Swagger is so valuable that if you don't publish Swagger docs for your API, *you don't have a product.*
- Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. Swagger is so valuable that if you don't publish Swagger docs for your API, you don't have a minimum viable product.
- Also note that your title differs from your question body. Swagger docs and the Swagger UI are different things. My answer applies to your question body.
#1: Initial revision
by
Kevin Krumwiede
·
2024-01-07T18:28:22Z (10 months ago)
Disabling Swagger docs is a terrible idea even for a public API. Swagger saves the consumer an enormous amount of development and testing. Swagger is so valuable that if you don't publish Swagger docs for your API, *you don't have a product.*