[Feature] RPC - OpenAPI
While moving into working on some real documentation for the RPC, we've come to the conclusion that we want to use the OpenAPI spec for the RPC, for both documentation and regular use. OpenAPI is a widely used and standardized format for API endpoints.
While we can introduce OpenAPI routes for the existing RPC, the version 5 of RPC response data does not cohere with OpenAPI response schema requirements.
I propose:
- Add OpenAPI front-end uri routes for RPC v5
-
type=info
: !544 (merged) -
type=search
: !544 (merged)
-
- During the next version of RPC (v6), we should define an openapi spec for the FastAPI project and modify RPC's response data to use it.
- In the future, we stick with OpenAPI front-end uri routes and schema formats
Edited by Kevin Morris