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 think it might be a good option for us as well, both for ease of maintenance and correctness. The Rust generator is using reqwest as we already do.
We could only use it internally, and keep exposing the same public API so it won't break any user code.
With that and #80, I think we could get rid of most of our unmaintained dependencies
The text was updated successfully, but these errors were encountered:
It's a great Idea but I wanted to do some tests regarding this and the generated openapi.json is missing a lot of responses objects which render the generated code unusable for some endpoints.
Thanks a lot for digging this up! That's quite sad that they don't want to fix this. Maybe there is still some value to use the client generated request types with our handcrafted response types?
It would be interesting to see if the official openAPI generated clients, go and C#, have since implemented any workaround for the concerned endpoints.
The new official vault C# client use a generated client based on the OpenAPI specs.
I think it might be a good option for us as well, both for ease of maintenance and correctness. The Rust generator is using
reqwest
as we already do.We could only use it internally, and keep exposing the same public API so it won't break any user code.
With that and #80, I think we could get rid of most of our unmaintained dependencies
The text was updated successfully, but these errors were encountered: