Expand description
incin-lsp - a transparent LSP proxy that sits between an editor and
rust-analyzer: it spawns rust-analyzer as a child process and rewrites
only the selected diagnostic and type-display messages through
incin-diagnostics before forwarding them on:
- pushed and pulled diagnostics: each message gets its typenum expressions replaced with decimals and known shape errors gain focused guidance;
textDocument/inlayHintresponses: each hint’slabelgets the same treatment viaincin_diagnostics::humanize_inlay_label;textDocument/hoverresponses: displayed type signatures are humanized.
Every other message (completion, goto-definition, formatting, …) is forwarded byte-for-byte unchanged - the proxy never re-serializes a message it isn’t rewriting, so it cannot introduce whitespace/key-order drift on anything it doesn’t touch.
Deliberately does not depend on tower-lsp/lsp-types: modeling the
entire LSP surface would be an ongoing maintenance burden for a proxy
that only needs to understand a small set of message shapes. Frames are
read/written as raw Content-Length-prefixed bytes (frame) and, only
when a rewrite might apply, inspected as serde_json::Value
(rewrite) - everything else passes through as opaque bytes.
Modules§
- config
- Runtime configuration, read once from the environment at startup - this is a developer-machine proxy launched by an editor, not a deployed service, so a config file would be more machinery than the surface needs.
- frame
- Raw LSP
Content-Length-framed message I/O, independent of any JSON-RPC type modeling - the proxy only needs to locate each message’s byte span, not parse its structure, to forward it. - rewrite
- Pure JSON rewriting for the two LSP message kinds the proxy humanizes. Kept free of any I/O so it can be unit-tested without spawning a process.