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?

まず setConfig API と VS Code settings API を追跡し、設定変更がどこに永続化されるかを確認します。ApplyInMemory オプションが userThirdParty と checkThirdParty を settings.json に書き込まずに適用できれば完了です。issue ではファイルもテストも指定されていないため、まず関連する実装パスと検証パスを特定する必要があります。

索引モデルが issue の本文から書いたものです。