-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Live API on SwaggerHub #525
Comments
can we use Slate? it's what we're using for Tendermint |
Good idea to consolidate tools. Why did you choose Slate over OpenAPI though? |
no reason in particular. When I joined the company, Anton had just done: tendermint/tendermint#526 so when folks starting asking for RPC docs (tendermint/tendermint#691), sticking with Slate made the most sense. |
OpenAPI (Swagger) has the advantage, that you can directly use the queries against a node making it easy to play around or test the API. |
Zach and I agreed to try to use Slate for all API documentation as Slate is already setup and integrates into the code. |
update: neither of us has used both sufficiently to judge the pros and cons ... so we're gonna run with both for the time being and re-evaluate in the future |
* CacheKV speedups * Remove extra btree alloc --------- Co-authored-by: Dev Ojha <[email protected]>
The idea is to have links to the API on SwaggerHhub that reflect the versions of the API definition on develop and master on GitHub.
SwaggerHub has such features, but we need to downgrade the specification from version 3 to version 2 of the OpenAPI spec.
See: https://app.swaggerhub.com/help/integrations/github-sync > Considerations
Reference: #383
The text was updated successfully, but these errors were encountered: