You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I also approved the binary download in my macos settings).
This creates the gen/sdk/client directory but nothing else. openapi.yaml is a valid OpenAPI 3.1 source.
I'd like to try this tool with OpenAPI 3.1
Only when I turned on trace log level do I get:
$ ~/lib/kiota/kiota --loglevel trace -d openapi.yaml -l typescript -o gen/sdk/client
...
crit: Kiota.Builder.KiotaBuilder[0]
error generating the SDK: OpenAPI specification version '3.1.0' is not supported.
Note: Since this is not just a Trace message but a Critical message, it should be printed by default (default log level Warning) without having to use --loglevel trace
The text was updated successfully, but these errors were encountered:
Hi @DavidBiesack ,
Thanks for reaching out and for trying kiota.
Kiota relies on openapi.net to parse the documents which doesn't support 3.1 yet.
However there are plans to support it, and as soon as a release is out, we'll update it here.
As per the error message, is it not visible until you change the log level?
Thanks for the additional information. That helped uncover a bigger than expected bug in the logging of Kiota, I put #1594 together to address that. This issue will be closed when the PR gets merged. Feel free to open other issues if you run into other things.
I installed the binary for macos from https://github.com/microsoft/kiota/releases/download/v0.1.3/linux-x64.zip
(expand the zip into
~/lib/kiota
) and ran:(I also approved the binary download in my macos settings).
This creates the
gen/sdk/client
directory but nothing else.openapi.yaml
is a valid OpenAPI 3.1 source.I'd like to try this tool with OpenAPI 3.1
Only when I turned on trace log level do I get:
Note: Since this is not just a Trace message but a Critical message, it should be printed by default (default log level Warning) without having to use
--loglevel trace
The text was updated successfully, but these errors were encountered: