Our great sponsors
-
openapi-examples
The highest quality collection of up-to-date OpenAPI specifications for public APIs on the internet. This dataset also includes descriptions, categories, uptime metrics, and media assets for every API.
-
openapi-code-generator
A code generation tool for openapi 3 / 3.1 specifications written in typescript, primarily aimed at generating typescript clients and server stubs. Other target languages may be added in future.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
- Directory of SDKs: https://konfigthis.com/sdk/category/all/
For context, we are developer experience enthusiasts and know the pain of searching for an up-to-date SDK for an API, only to find abandoned projects or poorly documented libraries. If you are lucky, some hero developer has published a high-quality SDK, only to eventually fall out-of-date over time, as unpaid work can only last so long.
To generate all the SDKs, we created the highest-quality collection of OpenAPI specifications (https://spec.openapis.org/oas/latest.html) on the internet: https://github.com/konfig-sdks/openapi-examples (it's open and MIT licensed). It contains metadata about the API provider, media assets, response time logs, and the specification itself.
Every specification is modified to ensure that we can create high-quality SDKs. For example, we use LLMs to generate method names for every operation so that the generated SDKs feel natural to use. We then continuously use this dataset to generate SDKs using a generator we have developed over the past 16 months.
I’m excited to know if you have any thoughts or feedback! We also created a Discord server you can join here: https://discord.gg/BAUS4Xtb.
Congratulations on launching, you have some interesting ideas in there.
Using a LLM to generate missing operation ids isn't something I've tried, instead I simply combine http method plus path segments which at least guarantees uniqueness [1]. I do a similar thing for extracting and naming inline schemas based on the operation and media types [2].
How do you prevent naming collisions? And do you find the resulting names to be significantly better than a deterministic approached like I described?
I'll definitely checkout the curated specifications - always useful to get more high quality (and hopefully varied) specifications to test my code generator with, and the lint rules is a great idea - I've had to explain what patterns lend themselves well to code generation many times.
I'm on mobile so may have missed it, but looking at one of your typescript examples I couldn't see any runtime response body validation, is this something you're thinking about?
- [1] https://github.com/mnahkies/openapi-code-generator/blob/main...