editor needs lsp features

[DanielFGray]

• [ ] completions
  • [ ] context-sensitive completions
  • [ ] completion for identifiers in introspection
  • [ ] completion for identifiers in current document (not in introspection)
• [ ] hovers
  • [ ] table/column info
  • [ ] signatures for user-defined functions
  • [ ] signatures for postgres built-in functions
• [ ] diagnostics
  • [ ] detect trailing/missing comma
  • [ ] error when referencing undefined
  • [ ] schemas
  • [ ] tables
  • [ ] columns
  • [ ] types
  • [ ] functions
  • [ ] type mismatches
  • [ ] for operators [cannot compare uuid to int]
  • [ ] for functions [function expected uuid, received ..]
• [ ] go to definition

docs:

• LSP spec
• lsp-web-extension-sample

prior art:

• https://github.com/microsoft/vscode-postgresql/
• https://github.com/UniqueVision/plpgsql-lsp/

alternatives:

• https://github.com/supabase-community/postgres_lsp since it's written in rust, it will need some work (wasm compiling?) to be able to run in a browser and interact directly with pglite

[DanielFGray]

a lot of things are currently blocked by needing a parser

some options [roughly in order of decreasing preference]:

• parse using sql-parser-cst
  • blocked by https://github.com/nene/sql-parser-cst/issues/40
• parse using libpg-query
  • https://github.com/pganalyze/pg-query-emscripten needs types
• parse using wasm build of treesitter
  • see Parsing pgSQL with tree-sitter in WASM
• parse using textmate grammar included with vscode/monace
  • [seems possible not but no idea if the hooks exist to be able to grab identifiers and such from it]

[DanielFGray]

some features may also be blocked by https://github.com/microsoft/language-server-protocol/issues/1264