I've been writing REST services for a long time, but I've never used Swagger before, although I've been aware of it.
I'm coming into a new project that is using it, although perhaps not as well as it could. I see a bunch of operations that define api responses like this: @ApiResponse(code = 404, message = "Service not available"), @ApiResponse(code = 500, message = "Unexpected Runtime error") These are handled implicitly by the framework. The service implementation doesn't handle them at all. Is it reasonable for services to define these expected response codes when the service implementation itself would never produce them? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
