metals-vscode: Metals starts even when project is not a scala project
I’m using the metals vscode plugin, and it works great in my Scala / SBT projects.
However I see that metals is being started even when the directory I open is not a scala project.
This leads to the creation of a .metals directory in the project.
To Reproduce Steps to reproduce the behavior:
- Open a directory that is not a scala project
- Metals is starting
- .metals directory is created.
Expected behavior
- No .metals directory, or starting of metals at all.
Installation:
- Operating system: macOS
- VSCode version: 1.36.1
- VSCode extension version: 1.5.2
- Metals version: 0.7.0
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 28 (16 by maintainers)
Commits related to this issue
- Merge pull request #133 from scalameta/dependabot/npm_and_yarn/types/node-14.0.13 Bump @types/node from 14.0.12 to 14.0.13 — committed to kasiaMarek/metals-vscode by mergify[bot] 4 years ago
Nice catch, this is indeed a vscode issue. See https://github.com/microsoft/vscode/issues/73656
I’m not sure of what’s the best workaround
@virtualdvid Och, I think when it timeouts looking for pattern it activates the extension by default? 😮
"activationEvent":"workspaceContainsTimeout:**/scala/**"@virtualdvid I think that is the best option for now without regressing in the behavior. I believe this should really be fixed on the VS Code side.