Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not start elm langage server on newly created elm project when vscode is already open #297

Open
harmboschloo opened this issue Jul 7, 2022 · 0 comments

Comments

@harmboschloo
Copy link

Expected Behavior

When I start vscode in an empty folder and then create an Elm project I should be able to start the Elm Language Server.

Current Behavior

I can not start the Elm Language Server. The only way to start it is to disable and enable the extension or to restart vscode.

The 'Restart Elm Language Server' command also doesn't work. It gives an error saying command 'elm.commands.restart' not found.

Possible Solution

It would be nice to have a command to (re)start the Elm Language Server available even if there was no elm project when vscode started.

Or it would be ever nicer if the extension could detect the creation of an elm.json file automatically and start/refresh the language server.

Steps to Reproduce (for bugs)

  1. Open vscode in an empty folder
  2. Create an Elm project
  3. Try to start the Elm Language Server somehow

Context

When I start a new project my normal workflow is to create a new folder and then start vscode. Then I open the terminal inside vscode and create an elm project with elm init.

Your Environment

  • Version used: 2.4.1
  • Editor name and version (e.g. VSCode 1.36.1): VSCode 1.68.1
  • Environment name and version (e.g. node.js 5.4): node.js 16.15.1
  • Operating System and version: Windows 11 Home
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant