Clarify position semantics in textDocument/hover request (#2208)

* Initial plan

* Clarify position semantics in textDocument/hover request

Co-authored-by: dbaeumer <1931590+dbaeumer@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: dbaeumer <1931590+dbaeumer@users.noreply.github.com>
This commit is contained in:
Copilot 2025-12-09 14:42:39 +01:00 committed by GitHub
parent 55159b77ab
commit 0bbb893d04
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 0 deletions

View file

@ -2,6 +2,8 @@
The hover request is sent from the client to the server to request hover information at a given text document position.
When the client sends a hover request, the position typically refers to the position immediately to the left of the character being hovered over. For example, when a user hovers over a character `c` at offset `n`, the client typically sends position `n` (the position before the character). However, how servers interpret this position and what hover information they return is language and implementation specific.
_Client Capability_:
* property name (optional): `textDocument.hover`
* property type: `HoverClientCapabilities` defined as follows:

View file

@ -2,6 +2,8 @@
The hover request is sent from the client to the server to request hover information at a given text document position.
When the client sends a hover request, the position typically refers to the position immediately to the left of the character being hovered over. For example, when a user hovers over a character `c` at offset `n`, the client typically sends position `n` (the position before the character). However, how servers interpret this position and what hover information they return is language and implementation specific.
_Client Capability_:
* property name (optional): `textDocument.hover`
* property type: `HoverClientCapabilities` defined as follows: