setConfig api option to set only in memory

Personne n'a encore pris cette issue.

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?

Commencez par suivre l’API setConfig et l’API de paramètres de VS Code afin de déterminer où les modifications de configuration sont persistées. Le travail est terminé lorsqu’une option ApplyInMemory applique userThirdParty et checkThirdParty sans les écrire dans settings.json ; l’issue ne mentionne ni fichiers ni tests, les chemins d’implémentation et de vérification pertinents doivent donc d’abord être identifiés.

Rédigé par le modèle d'indexation à partir du texte de l'issue.