-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
refactor: rename deno
specifiers to internal
#17655
refactor: rename deno
specifiers to internal
#17655
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine to me, @dsherret any objections?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
lsp clients needs to be updated, go_to_def response for example now returns internal: instead of deno: |
@@ -3121,7 +3121,7 @@ impl Inner { | |||
.performance | |||
.mark("virtual_text_document", Some(¶ms)); | |||
let specifier = self.url_map.normalize_url(¶ms.text_document.uri); | |||
let contents = if specifier.as_str() == "deno:/status.md" { | |||
let contents = if specifier.as_str() == "internal:/status.md" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This breaks vscode_deno, which does a request to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sigmaSd the only thing I could find in some other clients was #17655 (comment) -- do you know of anything else? |
go to definition as well fails and I assume go to refenrece and type refernece, their answer uses the deno schema
|
It's broken in vscode too. cc @crowlKats -- maybe we should revert this for now |
To fix reports of breakage from #17655
To fix reports of breakage from #17655
atom-ide-deno will also break, but it's no big deal since Atom is no longer in development. :( |
Thanks. It was reverted in #17673 |
Glad to hear that! |
Ahead of work of adding deno specifiers to prevent issues & confusion, and for #17648