Fallback to / prioritize workplace settings

I use workplace settings instead of global settings for all my projects. This to make sure any developer can just clone my repository, install all recommended plugins and get started asap instead of wasting time setting up.

I just spend 20 minutes trying to get the language server working. It didn’t start because it couldn’t find my node runtime. It was ignoring the workplace svelte.language-server.runtime configuration because the global user settings already set to option to the default usr/something/something runtime location.

Idk if this expected behavior, my fault or whatever really. It happened and now I’m making this post.

Describe the solution you’d like If the language server fails to (re)start, check for any workplace settings and try those settings instead. Or prioritize the workplace settings over the users global settings.

Describe alternatives you’ve considered None.

Additional context Maybe I configured it myself and/or don’t understand the inner workings of vscode. I’m not familiar with any of the current conventions. If this is something people agree with, well… lets go! If not, consider this request not made I guess.

[jasonlyu123]

I try that but I can’t reproduce it. Also, I found that the setting UI would add extra escapes to the windows path separator. If you type C:\\Program Files\\nodejs\\node.exe it would save as C:\\\\Program Files\\\\nodejs\\\\node.exe.

[dummdidumm]

Closing as it cannot be reproduced / is the correct behavior.