Setting not Functional - Superbol: Cache in Global Storage

[hornepm]

Regardless if I have "superbol.cacheInGlobalStorage": true in my user settings it still creates _superbol/lsp-cache when using cobc. I want it to use my Global Storage instead. I am on Debian Linux

VSCodium
Version: 1.110.11631
Commit: 15f64632d228eb10e1df8e125cf3d2c7d44c0f06
Date: 2026-03-08T23:40:23.744Z
Electron: 39.6.0
ElectronBuildId: undefined
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.12.74+deb13+1-amd64

Superbol
Identifier
ocamlpro.superbol
Version
0.3.0

[nberth]

Thanks for the report. Once #549 is merged, the cache will lie in the global storage as soon as this configuration setting is set.

There will still be an underlying issue in that we currently restart the LSP server to take changes of some settings into account, and that restart operation currently creates the _superbol/lsp-cache file. Still, after setting superbol.cacheInGlobalStorage: true, the _superbol/lsp-cache can safely be removed and it should not re-appear afterwards. A fix for this unwanted behavior will follow later.

[GitMensch]

@prestonmhorne if you want to test that fix: get the matching fix from the artifact https://github.com/OCamlPro/superbol-studio-oss/actions/runs/23052276665?pr=549 and install from VSIX (which will update the current installed with the fixed version)

[hornepm]

I can confirm that I tested this fix by installing from VSIX and it correctly makes the cache lie in the global storage.