Currently we are using open-api generator with c#, go and typescript ( angular ) and all works fine. I will give a try to this as well, thanks for video.
How do you use the open-api generator to generate only the models (req/res) but not the client itself given that you have an open-api spec? (eg. if you would have it generate the contracts during the build)
But how do you ship the generated SDKs to your consumers? Can Kiota generate a c# library instead of just a folder so you can build a .dll or nuget package out of it?
Exactly! Kiota doesn't touch the project configuration because we know each is unique. We (the Microsoft graph team) use kiota to generate the Microsoft graph SDKs, so does GitHub, Red Hat and many others. So can you as well. You'll only need to create your project, add the dependencies and publish it.
@@VincentBIRET Yes I have created a "kiota step" in our source generator projects. I create a new dotnet project, add the kiota dependencies and then let kiota generate the code into this project. Then I can build and pack it as a nuget und use it where I need it.
targeting TypeScript with Kiota's own http client? while NSwag and OpenApiClientGen and others can generate client api codes for Angular and Aurelia etc. using the http client libs of those TS/JS framework. Targeting TypeScript alone may be generic for every js /ts frameworks/libs, however, isn't such approach making the app codes look a little odd?
I would say it's composable. It might not be as “plug-and-play” as other libraries, but I think it makes sense. I would not be surprised if someone extends it to Angular.
The idea is to provide the extensibility points so people can: - configure every detail they care about - swap parts if they are not happy with the default implementations we've provided - build integrations with frameworks, whether client side like angular or server side like Java spring
Great video, congratulations.
May we inject the class (and interface) in a scoped or transient service lifetime?
Yes, you can. But, it's still lacking documentation.
Check here:
github.com/microsoft/kiota/issues/3816
github.com/MicrosoftDocs/openapi-docs/issues/37
@@gui.ferreira, thanks for your quick response.
I like the NSwag, but Kiota seems much less verbose.
Play with it. 😉
It was a pleasant surprise to me.
Currently we are using open-api generator with c#, go and typescript ( angular ) and all works fine. I will give a try to this as well, thanks for video.
How do you use the open-api generator to generate only the models (req/res) but not the client itself given that you have an open-api spec? (eg. if you would have it generate the contracts during the build)
Let me know how did it go
@suleymanov1990 Any update so far?
But how do you ship the generated SDKs to your consumers?
Can Kiota generate a c# library instead of just a folder so you can build a .dll or nuget package out of it?
The idea is that you generate it inside a Project (csproj).
Then you can "dotnet build" or "dotnet pack".
Exactly! Kiota doesn't touch the project configuration because we know each is unique. We (the Microsoft graph team) use kiota to generate the Microsoft graph SDKs, so does GitHub, Red Hat and many others. So can you as well.
You'll only need to create your project, add the dependencies and publish it.
@@VincentBIRET Yes I have created a "kiota step" in our source generator projects. I create a new dotnet project, add the kiota dependencies and then let kiota generate the code into this project. Then I can build and pack it as a nuget und use it where I need it.
How does this compare to open api generator?
Hi, great video.
Is there a way to do it for a nuget package? Dotnet to java use
Do you mean generate a Java port from a .NET Client ?
targeting TypeScript with Kiota's own http client? while NSwag and OpenApiClientGen and others can generate client api codes for Angular and Aurelia etc. using the http client libs of those TS/JS framework. Targeting TypeScript alone may be generic for every js /ts frameworks/libs, however, isn't such approach making the app codes look a little odd?
I would say it's composable. It might not be as “plug-and-play” as other libraries, but I think it makes sense.
I would not be surprised if someone extends it to Angular.
The idea is to provide the extensibility points so people can:
- configure every detail they care about
- swap parts if they are not happy with the default implementations we've provided
- build integrations with frameworks, whether client side like angular or server side like Java spring
We use it for a comming product. And I really hope it will get released before our release 😅
Kiota?! You already have v1.11 released.
What is the name of the IDE you are using (not the VSCode)?
Hi! You can find my IDE setup here: ruclips.net/video/wQG_LntcAQQ/видео.htmlsi=H-ncZNm4cBmk4NSs
Thanks!
@@gui.ferreira thanks, I thought it's Rider, but did not guess with the 'new UI' :-)
@@TanvirMahmudRony It's Rider from the future 😜
thanks
You're welcome!