setConfig api option to set only in memory

Nadie ha tomado este issue todavía.

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?

Empieza rastreando la API setConfig y la API de configuración de VS Code para encontrar dónde se persisten los cambios de configuración. Se considera terminado cuando una opción ApplyInMemory aplica userThirdParty y checkThirdParty sin escribirlos en settings.json; el issue no menciona archivos ni pruebas, por lo que primero deben identificarse las rutas relevantes de implementación y verificación.

Escrito por el modelo de indexación a partir del texto del issue.