Perhaps because that’s gawd awful as we generate client stubs based on the OpenAPI spec. We don’t write clients by hand for API’s we generate them.
I would prefer a static JSON specification (build time) and accept an HTTP response to a failed route call rather than one generated from their router at runtime.
Imagine a developer trying to generate a client stub on a day that this JSON spec is “modified”, how would they know that they have a complete spec or not? That’s the problem with a “dynamic” specification. How do we know which days to generate a client stub for developing an application and which day not to?
EVE Swagger Interface this even says nothing about it, so much for the “status” API for the API.
“Provides a general health indicator per route and method” No it doesn’t. It doesn’t show this missing route as “red” so we cannot even rely on the meta get_status route for checking the API!