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

Allow access to bazel-bin symlink #51

Open
guw opened this issue Oct 19, 2023 · 0 comments
Open

Allow access to bazel-bin symlink #51

guw opened this issue Oct 19, 2023 · 0 comments

Comments

@guw
Copy link
Collaborator

guw commented Oct 19, 2023

Access to bazel-* symlinks is hidden in most IDEs because they cannot deal with them nicely.

So far we replicate the exclusion in VS Code, too. But since it doesn't do the indexing as Eclipse/IntelliJ it might be possible to open up visibility in the VS Code extension.

This would be in VS Code only. The language server would still ignore them because of the expensive Eclipse resource refresh underneath. However, that's probably ok since the use case should be mostly browsing files in there.

On thing to verify is the interaction of VS Code with the LS in this case. For example, VS Code should not try to send requests for .java files inside the bazel-bin to the LS. If it does the LS needs to ignore those.

This should be limited to bazel-bin only. It should be visible by default unless an exclusion (-bazel-bin) is defined in the directories list in the project view.

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

1 participant