setConfig api option to set only in memory

[justarandomgeek]

My extension dynamically generates a library bundle and sets a path in userThirdParty and checkThirdParty: "ApplyInMemory", to allow the rest of my settings to be applied from the config.json, and library and plugin loaded, with minimal impact on the user's workspace. I currently set these two in the workspace via vscode settings apis, which leads to them being written to settings.json. Persisting these is undesirable as the userThirdParty path is a per-workspace path, which many users have complained about.

I noticed that the extension now provides a setConfig api, and was hoping to use this to provide those settings only in memory, but it seems they are also written back out to settings.json when set this way.

Would it be possible to have an "ApplyInMemory" option on the setConfig api for this case?

[justarandomgeek]

oh, this would also help avoid errors in cases where i'm installing an updated version of the library/plugin bundle on startup, and luals starts trying to load the plugin (from the previously-saved settings) in the middle of me replacing all the files, causing a plugin error. if it were provided only in memory, then luals would only see the settings after the files are all in place!