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 設定 API，以找出設定變更的持久化位置。當 ApplyInMemory 選項能夠套用 userThirdParty 和 checkThirdParty，而不將它們寫入 settings.json 時，即視為完成；該 issue 未指定檔案或測試，因此必須先確定相關的實作路徑和驗證路徑。