Nicolas Berthier

Closing in favor or more recent #321

Normally we should only have one `_superbol` next to a `superbol.toml`, the latter defining the root of project directories. So they should not end up "everywhere". To be investigated further.

I agree with the idea to have this URI as a fallback if no `superbol.toml` is found. Note, though, that at the moment this `_superbol` directory is only used to...

> `superbol.toml` should not be required to use Superbol This is true when one only has the LSP in mind. But SuperBOL does not reduce to the LSP only. It...

TODO: - [x] Add a flag to enable using VSCode-provided storage on demand; - [x] Silence cache-related errors.

At the moment, the github workflow ignores the VSCode client: it mostly builds `superbol-free` and runs the tests. But it may be worth extending that workflow to build the VSIX...

> You may want to check if the LSP can correctly parse https://github.com/jnicholson/ITP-Advanced-COBOL-FINAL/blob/master/workspace/COBOL%20Final%20Project/G3-BLD-VFX-WISH.cbl now. Yes that file is now parsed correctly.

@Stevendeo we you say "remote", do you mean the LSP has no longer access to the file-system where the project source code is? If that's the case, I think quite...

While trying to build the VSIX, I get an error like: ``` ✘ [ERROR] Could not resolve "ws" _build/default/src/vscode/superbol-vscode-platform/superbol_vscode_platform.bc.js:50:41: 50 │ joo_global_object.webSocket = require("ws"); ╵ ~~~~ You can mark the...

> I'd say there is a missing dependency somewhere, I don't have any error > > EDIT : `$ npm install ws`? Yes I think that should be a dependency...