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
In source files in a Deno project, the VS code breadcrumbs bar has a path segment between the file path and the code structure with two options: "Deno" and "TypeScript." Presumably this is what it does when there are two extensions providing parses/symbols for the same file, or something. It's kind of distracting, though. I haven't noticed any difference in the symbols listed under Deno vs TypeScript so far.
Is there any way to disable TypeScript's breadcrumbs, either via settings or in the Deno extension itself, so I am not prompted to choose "Deno" or "TypeScript" every time I focus the breadcrumbs bar at the top level of a file?
Relatedly, is it normal that the TypeScript language server keeps running even when the Deno language server is being used? Is there some way to disable it, just for a Deno workspace? I can't find any setting that would do this.
The text was updated successfully, but these errors were encountered:
In source files in a Deno project, the VS code breadcrumbs bar has a path segment between the file path and the code structure with two options: "Deno" and "TypeScript." Presumably this is what it does when there are two extensions providing parses/symbols for the same file, or something. It's kind of distracting, though. I haven't noticed any difference in the symbols listed under Deno vs TypeScript so far.
Is there any way to disable TypeScript's breadcrumbs, either via settings or in the Deno extension itself, so I am not prompted to choose "Deno" or "TypeScript" every time I focus the breadcrumbs bar at the top level of a file?
Relatedly, is it normal that the TypeScript language server keeps running even when the Deno language server is being used? Is there some way to disable it, just for a Deno workspace? I can't find any setting that would do this.
The text was updated successfully, but these errors were encountered: