lukaszraczylo ff37be1f17 fix(lsp): parse LocationLink in definition results ...

We advertise textDocument.definition.linkSupport=true, so gopls and rust-analyzer return the LocationLink shape (targetUri/targetRange). The old code only tried []Location then a single Location; unmarshaling LocationLink JSON into []Location silently succeeds with zero-value URIs/ranges, producing garbage locations (or a false 'No definition found'). parseDefinitionResult now decodes a unified shape capturing both field sets and normalizes to Location, and surfaces a real parse error instead of swallowing it. Adds TestParseDefinitionResult covering all shapes.

2026-06-20 00:33:31 +01:00

..

client.go

fixup! Update, bugfixes on diff and edit handling

2026-02-22 14:03:54 +00:00

definition_parse_test.go

fix(lsp): parse LocationLink in definition results

2026-06-20 00:33:31 +01:00

manager_test.go

fixup! Update, bugfixes on diff and edit handling

2026-02-22 14:03:54 +00:00

manager.go

fix(lsp): parse LocationLink in definition results

2026-06-20 00:33:31 +01:00

types.go

Ho hum.

2026-01-18 18:40:26 +00:00