The leap from swagger 1.6.2 to swagger 3 (OpenAPI 4) could be quite huge. The longer we wait, the more challenging the eventual upgrade becomes. OpenAPI 4.0’s release date isn’t guaranteed (correct me if i am wrong) where by even after release, it’s usually wise to wait for the ecosystem to stabilize in order to see community adoption and tool support before migrating.
The idea is to really first having it
- upgraded,
- clean up the SwaggerSpecificationCreator class by removing all unnecessary and deprecated methods,
- Think of bringing on board all the modules that aren’t currently extending our standard rest web services (i.e appointments, etc).
- and then we are ready for an autogenerated typescript client using swagger or generally autogenerating clients (programming language-agnostic)