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

fix: Don't instantiate CompletionItemProvider when using a language server #440

Conversation

cameron-martin
Copy link
Collaborator

Instantiating and refreshing the CompletionItemProvider is very expensive with large repos, due to it querying all targets from the repo. When using a language server the CompletionItemProvider is not even registered, so we avoid instantiating and refreshing it in this case.

Relates to #395.

…erver

Instantiating and refreshing the `CompletionItemProvider` is very expensive with large repos, due to it querying all targets from the repo. When using a language server the `CompletionItemProvider` is not even registered, so we avoid instantiating and refreshing it in this case.

Relates to bazel-contrib#395.
@cameron-martin cameron-martin merged commit 7b6f85f into bazel-contrib:master Feb 18, 2025
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants