Marking variable as global doesn't register

[NobleDraconian]

For some odd reason, when I mark a variable as 'global' in the extension settings, the extension seems to ignore the settings.

Here's an example of what I'm talking about.

As you can see here, I have custom globals defined in settings.json.

However the warnings for undefined globals are still showing, even after re-opening VSCode.

[sumneko]

.vscode should be placed at the root directoy of your workspace.

[NobleDraconian]

In the event of multiroot workspaces, you have to define the globals in the workspace file itself. The plugin writes settings to whatever the current root folder is.
The plugin should detect if the workspace is multiroot or not. If it is multiroot, it should define the global variable settings in the workspace file.

[sumneko]

Thanks, I will try to support this.

[sumneko]

I have did something with it and will present in next version. Now if your workspaces have multiroots, the language server will always use the settings of the first root.
It doesn't really solve the problem, because the server dose not fully support multiroots for now. Support for multipleroots is already planned, but with low priority, it may take a long time to fully address this issue.

[sumneko]

Has supported multi workspace.