diff options
| author | Adam Malczewski <[email protected]> | 2026-06-24 19:24:05 +0900 |
|---|---|---|
| committer | Adam Malczewski <[email protected]> | 2026-06-24 19:24:05 +0900 |
| commit | d4ff45c8a5c8aa37e824e63037874c46de877309 (patch) | |
| tree | 24f3628da58febbe1520c582d260e06349f47ced /GLOSSARY.md | |
| parent | e03a96e539d354345cd6328ddc5c7638398d3e14 (diff) | |
| download | dispatch-d4ff45c8a5c8aa37e824e63037874c46de877309.tar.gz dispatch-d4ff45c8a5c8aa37e824e63037874c46de877309.zip | |
fix(tool-edit-file): lazy LSP service lookup — diagnostics now actually work
The previous fix (e03a96e) wrapped getService in try/catch to prevent the
activation crash, but that wasn't enough: tool-edit-file activates at position
5 in CORE_EXTENSIONS while lsp activates at position 20. So getService ALWAYS
threw at activation time, lspService was ALWAYS undefined, and the diagnostics
hook was NEVER wired — edits succeeded but never showed LSP feedback.
Fix: make the LSP service lookup LAZY — defer it to edit time (when the tool is
actually called), not activation time. By then all extensions have activated.
The diagnostics function tries getService on each edit call; if LSP isn't
loaded, it returns a no-op (graceful degradation).
Diffstat (limited to 'GLOSSARY.md')
0 files changed, 0 insertions, 0 deletions