sublimelsp / lsp-deno Goto Github PK

I cannot make "deno.config": "path/to/cfg.json" to work. Tried both absolute and relative paths.
The config works when called directly: deno fmt --config, but is ignored when in the settings and using the LSP format — the indentWidth etc is ignored.

Config:

{
  "fmt": {
    "options": {
      "useTabs": false,
      "lineWidth": 80,
      "indentWidth": 4,
      "singleQuote": true,
      "proseWrap": "preserve"
    }
  }
}

I'm not sure how feature-complete LSP's Signature Help popup is supposed to be, but in this instance, if that block was rendered in monospace (doesn't necessarily need to be syntax highlighted) it would be a lot better.

Deno v1.15.3
ST 4121 + LSP v1.13.0

When you quit ST, then open ST, Deno has trouble handling requests for the open virtual views. This seems to be because it expects the client to request deno/virtualTextDocument before any other request for those kinds of virtual views. See: denoland/deno#11232

Is it possible to enable the --compat mode?
Deno exits with 1 if it's added to the command section of the settings. (The required unstable flag was enabled, so it's not the issue).
Is there any other way to pass the flag?

it seems LSP-Deno and LSP-typescript are enabled at the same time.

And here is my .sublime-project:

{
	"folders": 	[
		{ "path": "." }
	],
	"settings": {
		"LSP": {
			"Deno": {
				"settings": {
					"deno.enable": true
				}
			}
		}
	}
}

Describe the bug
I'm not sure if this is a bug or user error, but my project settings for Deno import maps are not overriding default language server settings for LSP-Deno.

To Reproduce

1. Create a Deno import-map file, e.g.:

   {
     "x/": "https://deno.land/x/"
   }

2. Create a new typescript file and attempt to import something using the import mapping:

   import { Application, Router } from 'x/oak/mod.ts';

3. LSP-Deno reports error:

   relative import path "x/oak/mod.ts" not prefixed with / or ./ or ../ Imported from "file:///path/to/file.ts"

Expected behavior
No error is reported and type checking works properly as though the import path were https://deno.land/x/oak/mod.ts

Environment (please complete the following information):

• OS: Windows 10
• Sublime Text version: 4107
• LSP version: 1.6.1
• Language servers used: Deno

Additional context
My sublime-project file is as follows (the documentation and issues I looked at gave confusing and/or conflicting directions as to where to put the setting so I have tried everything I can think of to get it to work, none of these do):

{
  "folders": [
    {
      "path": "."
    }
  ],
  "settings": {
    "deno.importMap": "./import-map.json",
    "LSP": {
      "deno.importMap": "./import-map.json",
      "clients": {
        "deno": {
          "deno.importMap": "./import-map.json",
          "settings": {
            "deno.importMap": "./import-map.json"
          }
        }
      },
      "deno": {
        "deno.importMap": "./import-map.json",
        "settings": {
          "deno.importMap": "./import-map.json"
        }
      }
    }
  }
}

I spent an embarrassingly long amount of time looking at rubbish LSP warnings before I realised the LSP-typescript ones were being presented, not the LSP-Deno ones :)

I've installed Deno and LSP but whenever I try to enable the Deno language server, it throws an error stated in the title of this issue.

OS: Linux Mint 21.2 Cinnamon

(My user configuration is the default one)

Hi! Thanks for a great package 💕

I'm 99% up and running with Deno in Sublime now, but I have this "One Last Thing"...

This is my project file:

{
    "settings": {
        "lsp_format_on_save": true,
        "LSP": {
            "LSP-typescript": {
                "enabled": false,
            },
            "Deno": {
                "enabled": true,
                "settings": {
                    "deno.enable": true,
                    "deno.config": "./deno.jsonc",
                    "deno.unstable": true,
                    "deno.suggest.imports.hosts": {
                        "https://deno.land": true,
                        "https://cdn.skypack.dev": true,
                        "https://esm.sh": true,
                    }
                }
            },
        },
    },
}

When saving this, I get this message in the LSP log panel:

failed to update settings: invalid type: map, expected a boolean

This indicates some violation of the JSON schema, I assume.

No warning border is shown in the UI though. If I change some other property, the LSP-json package will complain and show a yellow border at the location of the incorrect property.

If I remove the deno.suggest.imports.hosts property, the log line disappears.

But to me, the schema in this package seems correct, when checking https://github.com/sublimelsp/LSP-Deno/blob/main/sublime-package.json#L140 ?

Deno: Starting Deno language server...
Deno:   version: 1.18.1 (release, x86_64-apple-darwin)
Deno:   executable: xxx/.deno/bin/deno
Deno: Connected to "Sublime Text LSP" 1.15.0
Deno:   Auto-resolved configuration file: "file:///xxx/deno.jsonc"
Deno: language server initialized
Deno: Server ready.
Deno: failed to update settings: invalid type: map, expected a boolean
Deno:   Auto-resolved configuration file: "file:///xxx/deno.jsonc"

Let me know if this is not the correct location for this issue. Thanks!