Closed tschmittni closed 6 years ago
I wouldn't add the WebSocket-related parts at all. Swagger doesn't support WebSockets at the moment which makes this rather useless.
We document how to open a WebSocket connection in Swagger, and reference the action objects in the description for that route. I agree that they're useless in that you can't do WebSocket stuff in Swagger UI, or in generated clients, but you can at least view the schema for the actions, and our thinking was that that was better than nothing.
We also intend to support websockets in our codegen for services.
alright, sounds good.
Just removing unused definitions to fix some warnings.