When user enters their API page at apinf.io (e.g. https://apinf.io/apis/mau-lu)
they can expect a private API to be private.
However because of swagger-uis (the swagger rich preview functionality) default configuration,
the swagger of an API is always sent to swagger.io for validation
Also if an user has private API, they might want to not host it publicly. Currently
the only way to provide swagger documentation for the apinf platform is via a
swagger file that is publicly hosted on the web.
Swagger-UIs validation configuration should be discussed.
When user enters their API page at apinf.io (e.g. https://apinf.io/apis/mau-lu) they can expect a private API to be private. However because of swagger-uis (the swagger rich preview functionality) default configuration, the swagger of an API is always sent to swagger.io for validation Also if an user has private API, they might want to not host it publicly. Currently the only way to provide swagger documentation for the apinf platform is via a swagger file that is publicly hosted on the web.
Swagger-UIs validation configuration should be discussed.
This feature is documented here https://github.com/swagger-api/swagger-ui#parameters parameter validatorUrl.
User story
Resources
The following libraries may be used to validate OpenAPI documents on the client/server, from within our codebase:
-swagger-parser