mirror of
https://github.com/microsoft/language-server-protocol.git
synced 2025-12-23 08:48:16 +00:00
spelling: decide if
This commit is contained in:
parent
102eae9b4b
commit
ca2c1c2e4e
1 changed files with 1 additions and 1 deletions
|
|
@ -997,7 +997,7 @@ In addition to this moniker schemes starting with `$` are reserved and shouldn't
|
|||
|
||||
Ranges in LSIF have currently two meanings:
|
||||
|
||||
1. they act as LSP request sensitive areas in a document (e.g. we use them to decided of for a given position a corresponding LSP request result exists)
|
||||
1. they act as LSP request sensitive areas in a document (e.g. we use them to decide if for a given position a corresponding LSP request result exists)
|
||||
1. they act as navigation targets (e.g. they are the result of a Go To declaration navigation).
|
||||
|
||||
To fulfil the first LSIF specifies that ranges can't overlap or be the same. However, this constraint is not necessary for the second meaning. To support equal or overlapping target ranges we introduce a vertex `resultRange`. It is not allowed to use a `resultRange` as a target in a `contains` edge.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue