Labels: high-difficulty, lsp, backend, typescript
Difficulty: High
Module: apps/lsp-server/
🧠 Concept
Build a standalone Language Server Protocol (LSP) daemon in TypeScript that communicates with any LSP-compliant editor (Neovim, VS Code, JetBrains, Sublime).
⚠️ Problem
Building editor extensions individually for every IDE is inefficient; an LSP server brings GasGuard features to all developer environments simultaneously.
📁 Implementation Scope
apps/lsp-server/src/server.ts
apps/lsp-server/src/handlers/text-document.ts
🛠️ Requirements
- Implement standard LSP specification (
vscode-languageserver/node).
- Listen for
textDocument/didOpen, textDocument/didChange, and textDocument/didSave events.
- Return diagnostic array payloads and code action refactor proposals.
🎯 Acceptance Criteria
Labels:
high-difficulty,lsp,backend,typescriptDifficulty: High
Module:
apps/lsp-server/🧠 Concept
Build a standalone Language Server Protocol (LSP) daemon in TypeScript that communicates with any LSP-compliant editor (Neovim, VS Code, JetBrains, Sublime).
Building editor extensions individually for every IDE is inefficient; an LSP server brings GasGuard features to all developer environments simultaneously.
📁 Implementation Scope
apps/lsp-server/src/server.tsapps/lsp-server/src/handlers/text-document.ts🛠️ Requirements
vscode-languageserver/node).textDocument/didOpen,textDocument/didChange, andtextDocument/didSaveevents.🎯 Acceptance Criteria