-
Notifications
You must be signed in to change notification settings - Fork 199
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
Implement precise semantic token range requests and compare against current algorithm #9092
Milestone
Comments
maryamariyan
added a commit
that referenced
this issue
Aug 23, 2023
- Using feature flags Contributes to #9092
maryamariyan
added a commit
that referenced
this issue
Aug 23, 2023
- Using feature flags Contributes to #9092
This was referenced Aug 23, 2023
maryamariyan
added a commit
to dotnet/vscode-csharp
that referenced
this issue
Sep 6, 2023
- Changes data to take an array of arrays of number type Related to dotnet/razor#9092
davidwengier
pushed a commit
to dotnet/vscode-csharp
that referenced
this issue
Sep 8, 2023
- Changes data to take an array of arrays of number type Related to dotnet/razor#9092
Fixed by #9154 |
maryamariyan
added a commit
that referenced
this issue
Sep 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For Razor semantic range coloring, the LSP asks Roslyn to generate semantic tokens for a range from the 'earliest point' to the 'latest point' in the generated C# document that maps to the visible content. It has been suggested that the overall performance of the system will be faster if a set of precise calls are made instead of one encompassing call. We should implement this alternative and compare against the existing algorithm.
The text was updated successfully, but these errors were encountered: