|
|
|
|
|
by benatkin
1911 days ago
|
|
It's neither true nor false, it's an opinion. Sure "LSP" has support built in or tacked on (as plugins), mostly tacked on, to other editors. Nobody is required to assume TypeScript docs for a supposedly language-agnostic protocol, or that particular flavor of JSON-RPC, or JSON-RPC, or even JSON. And the pill I don't want to swallow, that people using LSP tend to swallow, is getting full definitions with autocomplete, or hover. Most of the time I prefer to just see completions when I autocomplete, not full definitions. It is clutter. |
|
There are also many different display/view methods that more sophisticated LSP implementations can implement. In my own LSP, we have different 'views' of the signatures/types/docs for
* hovers * signature completion * detailed type-level embedded docs in a separate pane
to name a few. It's entirely customizable.