-
Notifications
You must be signed in to change notification settings - Fork 145
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
Show breadcrumbs navigation when going to definition #850
Comments
I took at stab at that and it appears the problem is that the remote dependencies are marked as "read-only" files which makes them not available to display breadcrumbs. I need to dig more to figure out if this is something we can change or now. |
The other problem might be that we don't register a "file provider" for |
I did more digging and clicking on a I believe this is a limitation of VSCode in that it doesn't show breadcrumbs for this virtual documents. @dsherret suggested that we should allow to edit documents in the global cache, so I'm afraid this might be a "wontfix". |
One more possibility is using File System API seems to provide fs-like abstraction for custom handles. |
It's infeasible to do this for the global cache because we don't have a reverse mapping of file path to remote url. The upcoming |
Closes #20015 Closes denoland/vscode_deno#850 (only for deno_modules, but I don't think this will be possible for the global cache)
Is your feature request related to a problem? Please describe.
When I Go to Definition of a symbol from a deno.land (or any other HTTP source), an editor opens with a file where that symbol is defined. However, the editor does not have breadcrumb navigation (just below tabs) that allows to see file hierarchy in which this file resides. This makes it hard to explore new packages without leaving programming environment.
Describe the solution you'd like
A breadcrumb navigation should be accessible in editor visiting remote module. Because there are many Deno packages that have high quality code, it is often enough to go through source code to understand it. Currently one has to use external tools which breaks the flow for a programmer.
The text was updated successfully, but these errors were encountered: