-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
realtime beta api spec #341
Comments
I don't think that's possible. This spec is primarily designed for HTTP-based RESTful APIs. Realtime API is a WebSocket API not a RESTful one. |
@benadamdev there's no reason why it cannot be added. the only real difference is the protocol. Path and payload objects are still defined in json. I thought OpenAPI had websocket spec proposal? ... oh it was never accepted 😕 Well in either case it'd be great to have a machine readable spec for the json objects and paths 🤷 |
fwiw there are ways to use fastapi to build out ws paths... |
Found a realtime spec document, but it is unofficial |
@StephenHodgson Thank you very much for this. Although this not a REST API, the schemas section is a real gem from a code generation perspective. Coming from Microsoft, this is pretty official to me. Thanks again. |
Regardless if it is not a REST API, I think it is perfectly acceptable to add the schema object definitions to the OpenAPI spec here. |
Added in #356 |
Hi I was wondering when the reatime api spec will be added?
I see there are docs but wasn't able to find them in the current spec.
The text was updated successfully, but these errors were encountered: