You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should reintroduce the registry auto discovery we had in extension v2. Here is how it works:
When the LSP identifies an origin in a specifier for the first time it will try to fetch the well-known manifest for that origin. If a manifest is found, a message pops up asking the user if they want to enable import completions for that origin. If they press Yes the origin will be added to the deno.suggest.imports.hosts list and set to true. If they press no the origin will be added to that list, and set to false.
Example:
Auto discovery can be disabled with the deno.suggest.imports.autoDiscovery: false option. It is set to true by default.
The text was updated successfully, but these errors were encountered:
We should reintroduce the registry auto discovery we had in extension v2. Here is how it works:
When the LSP identifies an origin in a specifier for the first time it will try to fetch the well-known manifest for that origin. If a manifest is found, a message pops up asking the user if they want to enable import completions for that origin. If they press
Yes
the origin will be added to thedeno.suggest.imports.hosts
list and set totrue
. If they press no the origin will be added to that list, and set tofalse
.Example:

Auto discovery can be disabled with the
deno.suggest.imports.autoDiscovery: false
option. It is set to true by default.The text was updated successfully, but these errors were encountered: