-
Notifications
You must be signed in to change notification settings - Fork 483
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
Investigate exporting API documentation to Swagger format #1203
Comments
Next Steps
|
As a reference, just in case it is useful, swagger documentation is used for chainquery here. It is not complete yet but might be helpful. Also it can be done really easily now with the open api designer |
My understanding was that Swagger does not support JSONRPC, only REST. Is that true? Maybe that's not true anymore? |
OAI/OpenAPI-Specification#801 |
I saw that. It’s over a year old. Have you seen anything newer?
…On Thu, May 24, 2018 at 8:30 PM tiger5226 ***@***.***> wrote:
OAI/OpenAPI-Specification#801
<OAI/OpenAPI-Specification#801>
Looks like it didn't get into 3.0 spec.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1203 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAWJIL2SPt6QWE42mjKD2qEWEcdFxWy2ks5t11CKgaJpZM4T_nuX>
.
|
No I could not find anything on the status of that. There was communication where people said they hacked it in, but I didn't think we would want follow suite there. |
bitshares is having the same issue: bitshares/bitshares-core#792 |
(This ticket is possibly under- or incorrectly specified since I don't know very much about Swagger.)
lbry.tech will need to display the API documentation for lbry, lbrycrd, and potentially other projects like lighthouse.
Having all repositories that provide an API export their API signatures in a shared, open format will allow lbry.tech to display all APIs in a similar fashion.
The text was updated successfully, but these errors were encountered: