Expand description
Rich SQL hover.
Resolution order (first match wins):
- Column declaration when cursor sits on the column NAME inside a CREATE TABLE in the current buffer.
- Constraint / index / trigger identifier (pk_/fk_/idx_/…) – catalog lookup or fallback convention card.
- Catalog table / column / DB function.
- Multi-word SQL keyword (sliding window).
- Single-word knowledge entry (keyword / type / built-in function).
Modules§
- constraint_
id - Hover for constraint / index / trigger identifiers.
- ddl
- Lookups against the current buffer’s CREATE TABLE statements.
- implicit
- Derive implicit column specs that the user did not type but the DB still applies.
- md_
table - ASCII tables for hover output, with single-row separators so the markdown renderer can colour-style the grid uniformly.
- render
- Markdown renderers for hover bodies.
- resolver
- Pick the right hover renderer for the token / word run under the cursor.
- token
- Locate the identifier or word run at the cursor.
Enums§
- Keyword
Case - How keywords are cased in synthesized DDL fragments shown in hover.
Functions§
- current_
keyword_ case - hover
- hover_
with - Like
hoverbut applies the caller’s preferred keyword casing to every synthesised DDL fragment. - hover_
with_ parsed - Like
hover_withbut takes an already-parsedfile, so a caller that maintains a per-document parse cache (dsl-server’sParseCache) can skip re-parsing the whole buffer on every hover request.hover_withitself parses fresh and delegates here.