Skip to content
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

Support for URIs from Custom File System Providers #48

Open
gbrueckl opened this issue Sep 28, 2023 · 2 comments
Open

Support for URIs from Custom File System Providers #48

gbrueckl opened this issue Sep 28, 2023 · 2 comments

Comments

@gbrueckl
Copy link

Is your feature request related to a problem? Please describe.
In some of my extensions I use custom filesystem providers to load files and folders from a remote source. Unfortunately, the built-in Outline view in VSCode does not support those so I was hoping that your extension might be able to help and load outlines also from custom URIs

Describe the solution you'd like
The outline for files from remote URIs should work the very same way as it does for local files

Describe alternatives you've considered
Waiting for the built-in outline to support remote URIs
tried other outline/codemap extensions without success

Additional context
Loading the outline from a local file:
image

Loading the outline for the very same file from a custom filesystem provider (dbws:/myLibrary.py)
image

if you are translating the URI from the TextEditor/Document to a local fsPath, thats probably the issue

@Gerrnperl
Copy link
Owner

Gerrnperl commented Oct 10, 2023

Actually, I'm simply calling the same symbol source as the built-in outline. No analysis of the code was done.

Therefore, in most cases the symbols displayed by this extension are consistent with the built-in outline. In other words, I just made a different outline from the UI level.

This problem should be solved by custom file system extensions or vscode (aka, symbol information provider)

I may try to analyze this issue, but there is no guarantee that it will be solved.

@gbrueckl
Copy link
Author

I could not find any settings I could do in my custom file system extension to support this so I guess thats something internal to VSCode then that would need to be changed to support URIs (ur custom file systems in general)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants