-
Notifications
You must be signed in to change notification settings - Fork 168
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
Add support for handling OpenAPI v3.1 definitions #3914
Comments
Hi @julealgon, |
@baywet Once OpenAPI 3.1 support is finalized, is support for generation of webhooks planned? I currently maintain https://github.com/octokit/webhooks.net manually, but am eager to switch over to automatic generation if possible. |
@JamieMagee if by generation of webhooks you mean generating the models for the incoming requests, sure we could add that. |
@baywet yes, that's exactly what I am talking about. A top level
As of release Footnotes |
Thanks for clarifying! |
Hello, |
Yes! It's absolutely something we'll start working on soon as there is a lot of demand for it! We have some other priorities right now but this should be in the next bucket of improvements! |
We started using Kiota recently for a new integration, but the OpenAPI definition for the API we were to interface with uses the v3.1 OpenAPI spec. When attempting to generate a client for this spec, we get the following error message:
This forced us to down-convert the definition from v3.1 to v3.0 to be able to use Kiota to generate a C# client for it.
We'd like for Kiota to be able to handle OpenAPI v3.1 natively, so that we don't have to perform this extra, lossy conversion step. The conversion increases maintenance substantially for us, since now we cannot refer directly to the target API's OpenAPI definition, and instead, forces us to maintain a local converted definition file ourselves. Additionally, whenever the target API definition changes in any way, we are then required to perform the conversion step manually again and update our converted file, to only then be able to run Kiota on it again to generate the updated proxy.
For reference, this is the definition we are currently targeting (from SendGrid):
The text was updated successfully, but these errors were encountered: