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

Collect inlay hints during combined requests #2588

Merged
merged 1 commit into from
Sep 20, 2024

Conversation

vinistock
Copy link
Member

Motivation

We should be collecting and caching inlay hints as part our combined requests. That way, we only perform the work once per document state and if the user keeps scrolling the document, we just filter the ones to show based on the given range.

This prevents another AST traversal and improves our performance on user edits.

Implementation

The idea is to collect and cache inlay hints during the combined requests, but we still keep the request itself separate so that we can apply the range if user is scrolling up and down.

Automated Tests

Current tests should cover it.

@vinistock vinistock added enhancement New feature or request server This pull request should be included in the server gem's release notes labels Sep 20, 2024
@vinistock vinistock self-assigned this Sep 20, 2024
@vinistock vinistock requested a review from a team as a code owner September 20, 2024 18:41
@vinistock vinistock requested a review from andyw8 September 20, 2024 18:41
@vinistock vinistock force-pushed the vs-run-inlay-hint-with-combined-requests branch from 49bc151 to 984948f Compare September 20, 2024 19:49
@vinistock vinistock merged commit 8ce513c into main Sep 20, 2024
37 checks passed
@vinistock vinistock deleted the vs-run-inlay-hint-with-combined-requests branch September 20, 2024 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server This pull request should be included in the server gem's release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants