setConfig api option to set only in memory

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?

Inizia tracciando l'API setConfig e l'API delle impostazioni di VS Code per individuare dove vengono mantenute le modifiche alla configurazione. Il lavoro è completato quando un'opzione ApplyInMemory applica userThirdParty e checkThirdParty senza scriverli in settings.json; l'issue non indica file né test, quindi è necessario identificare prima i percorsi rilevanti per l'implementazione e la verifica.