Open erwinkramer opened 1 day ago
Hi @erwinkramer Thank you for using kiota and for reaching out.
This is by design, we want to make the clients more portable with this iteration. What's odd for you in terms of experience, is that there's no documentation on the migration process and the vscode experience is providing the new workspace system while the CLI is still using the lock experience. We're working on planning, to official bump the version to a v2 and clean this up.
Trying using DefaultRequestAdapter from Microsoft.Kiota.Bundle instead that should get your application working again.
Let us know if you have any additional comments or questions.
What are you generating using Kiota, clients or plugins?
API Client/SDK
In what context or format are you using Kiota?
Nuget tool
Client library/SDK language
Csharp
Describe the bug
I had a lock file like this, generated by the CLI tool:
Then i decided to remove the CLI tool and go with the VSCode extension. This resulted in the extention asking me if i want to convert to a workspace-based Kiota setup, fine, i press OK. This results into the following workspace:
Now i re-generate the client-code by pressing "Re-generate" in the workspace.json.
At this point, my client differs, the following lines are removed in my client:
And results in the error at runtime (compiles just fine):
which makes sense considering there was an addition (which Kiota decided it needed while using the CLI) in the lock file which didn't get ported over to the workspace:
Expected behavior
Should be a working and smooth transition.
How to reproduce
Working setup is at https://github.com/erwinkramer/bank-api?tab=readme-ov-file#bank-api
Open API description file
No response
Kiota Version
1.20.0+81bdb1bf13383a749f794d47926d09733d2d7be1
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
Debug output
No response
Other information
No response