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

deno lsp #8400

Closed
bartlomieju opened this issue Nov 16, 2020 · 0 comments · Fixed by #8515
Closed

deno lsp #8400

bartlomieju opened this issue Nov 16, 2020 · 0 comments · Fixed by #8515
Assignees
Labels
cli related to cli/ dir feat new feature (which has been agreed to/accepted) user feedback wanted feedback from the community is desired

Comments

@bartlomieju
Copy link
Member

bartlomieju commented Nov 16, 2020

Tracking issue for deno lsp subcommand.

Given that a lot of code in vscode_code duplicates logic inside deno binary (eg. module resolution algorithm, DENO_DIR path hashing) it becomes obvious that deno should provide its own LSP.

Implementing LSP inside the binary should make maintaining the extension easier, as well as it will allow us to provide the same benefits and experience to other editors.

This feature is being worked on

@bartlomieju bartlomieju mentioned this issue Nov 16, 2020
22 tasks
@bartlomieju bartlomieju added cli related to cli/ dir feat new feature (which has been agreed to/accepted) user feedback wanted feedback from the community is desired labels Nov 16, 2020
@kitsonk kitsonk self-assigned this Nov 16, 2020
kitsonk added a commit that referenced this issue Dec 7, 2020
@jeiea jeiea mentioned this issue Dec 27, 2020
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli related to cli/ dir feat new feature (which has been agreed to/accepted) user feedback wanted feedback from the community is desired
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants