Implement OpenAPI compliance #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We want to make our own lives easier and others' as well. Being OpenAPI compliant means we can generate machine readable information about our API, which has downstream benefits. This includes generating API documentation pages (for example, with Swagger) and potentially even whole Software Development Kits (SDKs), I am learning now.
The benefits need to be better researched, but even if it is only the documentation website/pages that can be generated it is already worth a lot! This issue tracks the work and is a place to share resources.
https://openapi.tools
https://buildwithfern.com/
https://www.speakeasy.com/
It seems like the best choice to do this is with the crate
utoipa
👍See also #10 for an outdated trial that seemed decent.