Implement OpenAPI compliance #1

Open
opened 2025-07-18 11:46:02 +00:00 by chartgerink · 2 comments
Owner

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/

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/
Author
Owner

It seems like the best choice to do this is with the crate utoipa 👍

It seems like the best choice to do this is with the crate [`utoipa`](https://github.com/juhaku/utoipa) 👍
Author
Owner

See also #10 for an outdated trial that seemed decent.

See also #10 for an outdated trial that seemed decent.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: libscie/researchequals-api#1
No description provided.