Disclaimer: I haven't read many docs beyond this project's README. However, it was mostly not needed—I had a few minor issues, all fixed through restarts/cleaning caches.
TL;DR. It seems this plugin should declare scalaLanguageServer.logLevel and scalaLanguageServer.heapSize to VSCode but doesn't, so VSCode warns about those settings with "Unknown configuration setting", even though they work fine.
Details
I added the following content in my settings, based on tooltips and this plugin's docs:
I don't really understand the current configuration, but it seems to indeed not declare those settings.
It seems the setting might still work—jps finds (among others) these running JVMs, and I suspect the latter has vscode.logLevel=DEBUG because of my setting. The former seems an instance of #2 (I also got errors on locks being held, worked around by moving away the Ensime cache).
Disclaimer: I haven't read many docs beyond this project's README. However, it was mostly not needed—I had a few minor issues, all fixed through restarts/cleaning caches.
TL;DR. It seems this plugin should declare
scalaLanguageServer.logLevel
andscalaLanguageServer.heapSize
to VSCode but doesn't, so VSCode warns about those settings with "Unknown configuration setting", even though they work fine.Details
I added the following content in my settings, based on tooltips and this plugin's docs:
However, the two latter settings (either in the user settings or workspace settings) give warnings such as:
Googling only found the same warning for other plugins. Browsing VSCode docs suggests available config settings should be declared following this example: https://code.visualstudio.com/docs/extensionAPI/extension-points
I don't really understand the current configuration, but it seems to indeed not declare those settings.
It seems the setting might still work—
jps
finds (among others) these running JVMs, and I suspect the latter hasvscode.logLevel=DEBUG
because of my setting. The former seems an instance of #2 (I also got errors on locks being held, worked around by moving away the Ensime cache).Indeed, changing those settings, closing the folder and reopening it leads to the following JVMs:
Where the settings for PID 96701 are the ones I specified.