Mark Li

I moved all the testing stuff to https://github.com/psalm/psalm-vscode-plugin/pull/269 because it was getting tough to read, and also I don't have any actual tests yet.

https://github.com/vimeo/psalm/issues/10094 prevents multiple LSP instances currently

You can start a codespace in https://github.com/limarkxx/psalm-vscode-plugin/tree/test-folder-level-settings to test with a sample project

Maybe but it should at least be something at least slightly challenging for psalm to munch on. Perhaps put those files in https://github.com/psalm/sample-laravel-app and https://github.com/psalm/sample-slim-webapp, and use git submodules to...

I believe the desired effect is in a [multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces), config settings which are relevant to Psalm should have a [scope](https://code.visualstudio.com/api/references/contribution-points#Configuration-property-schema) of `resource` or `machine-overridable` instead of `window`. In other...

@tm1000 I've set https://github.com/psalm/psalm-vscode-plugin/pull/268 as a draft PR