Roadmap 3.0

[kitsonk]

With the release of 3.0 version of the extension, there was a significant re-write leveraging the LSP server built into the Deno CLI. We focused on making the initial release of the v3.0 extension as an "MVP" but there are certain features that we need to add/restore/rebuild as well as improvements overall to the extension.

There are quite a lot of features that are either fully provided by a LSP server, or require significant work there to enable them in the extension. There is an existing issue in the Deno CLI to track those: denoland/deno#8643

Here is a list of functionality that we want to add to the extension. Those marked with a 🦕 are mostly/fully things that need to occur in the Deno CLI:

• Import auto-completion 🦕
  • With custom remote registry auto-completion 🦕
  • Configuration of remote registries
  • A "helper" to configure remote registries
• workspace folders 🦕
• Debug/Inspector Integration
• deno test integration via code lens (feat: add support for tasks and test code lens #436) 🦕
• dependency tree explorer 🦕
• refactoring fixes (see: Make refactoring available #433) 🦕

[what1s1ove]

Hey @kitsonk,
Am I doing something wrong? ☹️

Thanks for all you do!

[kitsonk]

@what1s1ove both the new version of the extension and the version of Deno that supports it are not released yet. They will be released sometime in the next 24 hours.

[tatemz]

I see "workspace folders" is completed but have workspace-folder specific settings been confirmed to be working? I know the docs say each workspace folder must have a .vscode folder with the settings.json contained in it, but the VS Code Workspace configuration API supports an alternative setup to use folder config settings. Correct me if I am wrong.

I cannot seem to get the following workspace configuration to properly work:

{
	"settings": {
		"deno.enable": false,
		"deno.lint": true,
		"deno.unstable": true,
		"deno.codeLens.implementations": true,
		"deno.codeLens.references": true,
		"deno.suggest.autoImports": true,
		"deno.suggest.completeFunctionCalls": true,
		"deno.suggest.names": true,
		"deno.suggest.paths": true,
		"deno.codeLens.referencesAllFunctions": true,
	},
	"folders": [
		{
			"name": "My Python Folder",
			"path": "./my-python-folder"
		},
		{
			"name": "My Deno Folder",
			"path": "./my-deno-folder,
			"settings": {
				"deno.enable": true,
				"deno.importMap": "${workspaceFolder}/import_map.json"
			}
		},
	]
}

Maybe the above configuration is not supported or not on the roadmap, but I want to ensure that is true before making an issue.

[kitsonk]

@tatemz sorry, it was pulled from 1.10.0 because of a late breaking issue and needs to be re-landed. The extension side is all ready to go.

[kitsonk]

This issue has reached the end of its usefulness, so I am going to close.

I opened #470 and #433 was already opened.

The extension and the language server are tightly coupled together, you can see the current roadmap for the language server as part of the roadmap for the CLI (see: denoland/deno#11168).