Fix resolved lens causing flickers#56047
Merged
Merged
Conversation
Veykril
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on #54100 (comment)
Adjusts the code lens display closer to what VSCode does: have blank placeholders for the code lens need resolving.
Zed will remove them if resolve returns nothing, so some small amount of jitter is still there.
Also reworks LspStore layer to provide a simple resolve method, without any ranges involved, grouping that logic in the editor itself.
This allows to process each resolve request separately, updating editor blocks as soon as possible.
Before:
before.mov
After:
after.mov
Release Notes: