Microsofts "Wide World Importers" sample database has a "real life" complexity, and I have written an ASP.NET Core OData service for it last year: https://github.com/bytefish/WideWorldImporters.
I have just updated the solution to use Kiota for building an Api Sdk, and it generated a working client out of the box.
To the Kiota team: I am very, very impressed with the ease of use and the quality of the generated client.
Last week, we released #kiota 1.8, bringing many key improvements (API Manifest, Raw URL support, primary error messages support, more OpenTelemetry support) and promoted 2 new languages to stable, PHP and Python! Install the CLI or the VS Code extension! https://slevert.me/46ZenLg
#openapi specifications are tricky. At some point a generator is involved and generators only seem to make the job 90% right. When the spec is generated I regularly see parts missing. That's why teams write those specs manually. But latest when implementing clients, generators are involved again, making the job again only 90% right.
I do not know how to approach it best. Generate clients once and then update them manually with each specification update?
@noordsestern Client code generators are only 90% right because a) most generator efforts have been poorly funded b) many people who try writing them only understand 90% of OpenAPI c) they try too hard to meet everyone's style preferences.
We're trying to get to 100% with #kiotahttps://aka.ms/kiota but it is hard work. There are things we could change in OpenAPI to make it easier.
@darrel_miller thank you! I can imagine the challenges. With different versions of specifications and basically an infinite amount of target programming languages (and their versions!) i have deep respect for that it even works "only" 90% . It still is a huge help.
Use Kiota to create a custom C# client for the ChatGPT API! Don't rely on unofficial third-party packages and learn how Microsoft generate their Graph API SDKs.