Repository navigation
Conversation
This was referenced Sep 28, 2026
Coverage
|
indent
Bot
force-pushed
the
fix/git-show-repo-paths
branch
from
October 14, 2026 19:08
697c73a to
2f03c4d
Compare
indent
Bot
force-pushed
the
fix/lsp-hover
branch
from
October 14, 2026 19:08
916da7b to
2385923
Compare
indent
Bot
force-pushed
the
fix/git-show-repo-paths
branch
from
October 14, 2026 19:32
2f03c4d to
710aa95
Compare
indent
Bot
force-pushed
the
fix/lsp-hover
branch
2 times, most recently
from
October 14, 2026 19:54
616645a to
2d484e2
Compare
indent
Bot
force-pushed
the
fix/git-show-repo-paths
branch
from
October 14, 2026 19:54
710aa95 to
0ba0155
Compare
The server family pairs a native LOCATION with the MARKUP that follows it into one HoverRecord, but translate::hover pushed the markup first, so every hover failed with "LSP markup has no target location" (surfaced as Internal: no detail). Push the location first, as one group, and fall back to the empty range at the queried position when the language server reports no range.
indent
Bot
force-pushed
the
fix/git-show-repo-paths
branch
from
October 15, 2026 01:43
0ba0155 to
00305f6
Compare
indent
Bot
force-pushed
the
fix/lsp-hover
branch
from
October 15, 2026 01:43
2d484e2 to
bd7d77b
Compare
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
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.
Stacked on #26. The diff shows only this change.
Every
yas lsp hoverfailed withInternal: no detail, and hover in the browser editor showed nothing.Cause
The server family builds a HoverRecord from a native LOCATION followed by its MARKUP (
crates/server/src/yas_lsp.rsconvert_query_response), and the wire HoverRecord'stargetis that location.translate::hoverpushed the markup first. When the language server gave no range, it pushed no location at all. Every hover therefore failed with "LSP markup has no target location".Fix
translate::hovernow pushes LOCATION then MARKUP as one atomic group. When no range is reported, the location is the empty range at the queried position.PendingQuerynow carries the line and column for this.Testing
hover_location_precedes_markupcovers both the ranged and rangeless cases.cargo test -p yas-lsppasses (60 tests).Tag
@indentto continue the conversation here.