FAQ
These are not really questions. They are just some things to take note of. Well...
ghcSimple.workspaceType is removed. If you previously relied on the configuration ghcSimple.workspaceType to set up your projects, you should consider switching to one of the new schemes.
For a quick fix, you can set ghcSimple.replCommand and ghcSimple.replScope to appropriate values. For example, set ghcSimple.replCommand to stack repl or stack repl $stack_ide_targets for Stack projects, and set to cabal repl for Cabal projects.
See wiki page Project Configuration for details.
Please note that projects should be opened so that the top-level configuration file (stack.yaml, cabal.project, hie.yaml, etc.) is at the workspace root. This way the extension can detect the project correctly.
vscode-ghc-simple tries to watch for changes in crucial configuration files, such as stack.yaml, hie.yaml or *.cabal. It also honors the dependencies option in your hie.yaml.
If however it does not work and the sessions use stale configuration anyway, or if reasons other than configurations file changing causes stale configuration to be used, you can use the Restart GHCi sessions command in the Command Palette to manually restart the GHCi sessions. See Commands.
Common symptoms that would be solved by this include dependencies not appearing, or extensions specified in *.cabal or package.yaml not being enabled. If you are affected by this, and the need to restart can be detected from a workspace file change, you can add it to hie.yaml, or, if you are using implicit configuration, opening an issue.
The full log of interaction between GHCi and this extension can be found by clicking the 'GHC' item on the status bar:
When reporting an issue please also attach relevant log output, ideally (but not necessarily) from a fresh start (Developer: Reload Window command) to reproduction of the bug. You can also check there when things go unexpectedly.