Cannot enable backing store with visual studio extension

[ddyett]

Goal was to test out dirty tracking in python, but generating from the extension always set the backing store value to false even if i update the kiota.lock file. I needed to manually update the kiota lock file, then run kiota update manually.

[darrelmiller]

Yeah, we have run into a bit of a cyclical refresh issue with some recent changes where regenerating will overwrite settings you hand edited in the Kiota.lock file.

This will be addressed with the Kiota.config file that will cleanly separate user input vs what is output. I was writing the spec in a doc but I'm tired on not having good JSON editing abilities in word, so I'm just going to transfer it all to an issue here.

[baywet]

We have a number of settings that can't be passed through the generation dialog today.
But I don't feel like asking 12 questions during the generation would lead to a great experience.

We should probably register settings in vscode for those. They are defined by the user, sync across devices, and can be overridden by project.

Separately, when a lock is present, the extension should read/watch it before passing things back to the generator to avoid things set manually from being overwritten.

[baywet]

here is what the settings panel is starting to look like.

[sebastienlevert]

Priority order of setting:

1. kiota command line values (impacted by VS Code settings)
2. kiota command line default values

[baywet]

implemented. To your original question DeVere:

• things in kiota lock are always overwritten by what's in the vs code context (settings, answer to questions, default values for settings) during the generate commands.
• things in kiota lock are kept during the update command.
• you now have settings to set the backing store, etc...
• those settings can be overridden by repo thanks to how vs code settings work in general.