built-in language servers #10129
-
|
Hi! If we look at #2608 as the first attempt to implement new completion source - paths. It's use same structures and logic as for language servers completions And that why Helix can use language-server terms to implement
To implement this Idea needs to solve next major tasks
And this logic may be integrated with plugin system in language servers terms too. This idea isn't conflicting with Helix way? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This is reversed. LSP should fit into more generic Helix-specific types and systems rather than Helix re-using LSP types to implement other features. For example a diagnostic from a spell checker can fit into a core Diagnostic type. Custom snippets should share code with LSP snippets rather than custom snippets being implemented only in terms of LSP. Simulating language servers for features like spell checking is pure overhead and unnecessarily binds us to the LSP spec and its types. |
Beta Was this translation helpful? Give feedback.
-
|
Yep. I see. Solid bounds of LSP spec can be blocker in future |
Beta Was this translation helpful? Give feedback.
This is reversed. LSP should fit into more generic Helix-specific types and systems rather than Helix re-using LSP types to implement other features. For example a diagnostic from a spell checker can fit into a core Diagnostic type. Custom snippets should share code with LSP snippets rather than custom snippets being implemented only in terms of LSP. Simulating language servers for features like spell checking is pure overhead and unnecessarily binds us to the LSP spec and its types.