It's been decided that we need to drop support for optional path parameters in our swagger specifications to become swagger spec compliant. That will allow us to drop Wikimedia swagger-ui fork and switch to upstream UI. Additionally, we would be able to use new features of Swagger 3.
In case the service does not optional path parameters, the task is only about using new features of Swagger 3. In case optional parameters are used, each path should be split into several declarations with only required parameters. So,
/{foo}{/bar}{/baz}should become 3 paths:
/{foo}
/{foo}/{bar}
/{foo}/{bar}/{baz}In order to minimize copy-pasting, it's would be preferred to use swagger 3 components feature or YAML references.
The resulting spec has to pass swagger spec validation.
- service-template - should be updated to depend on the upstream Swagger UI version.
- citoid
- cxserver
- eventstreams
-
graphoid(service was archived) - mathoid
- mobileapps - T218220: Make mobileapps & proton swagger spec compliant
- proton - T218220: Make mobileapps & proton swagger spec compliant
- recommendation-api