Apparently, the plugin would fail to initialize if you were starting VSCode without a workspace. I exclusively open folders as workspaces, so I never thought to test this scenario.
The failure is because the plugin was trying to find project.godot when it activated, and several things assumed that would never fail. I've completely removed this search from the plugin activation and every place that needs the project file/directory now just looks it up when it needs it.
This also means I can remove a dependency (klaw), which is always good.
This should be a fix for #435.
Apparently, the plugin would fail to initialize if you were starting VSCode without a workspace. I exclusively open folders as workspaces, so I never thought to test this scenario.
The failure is because the plugin was trying to find
project.godotwhen it activated, and several things assumed that would never fail. I've completely removed this search from the plugin activation and every place that needs the project file/directory now just looks it up when it needs it.This also means I can remove a dependency (klaw), which is always good.