Expand description
Markdown renderers for hover bodies.
Table hover ships both a column-list table AND a synthesised
CREATE TABLE block so the user sees the source-level shape (types,
NOT NULL, DEFAULT, FK targets) in one glance. Column / function /
column-decl hovers each have their own renderer.
Functions§
- column
- column_
decl - Render a column declaration with no implicit-spec data.
- column_
decl_ with_ implicit - Render a column declaration plus every implicit spec derived from the parent table (PRIMARY KEY -> NOT NULL + UNIQUE, FOREIGN KEY, SERIAL / IDENTITY -> NOT NULL + auto-increment). The result is the “full spec view” – declared + implicit, in one table.
- column_
in_ tables - column_
with_ catalog - Variant of [
column] that also lists every FK in the catalog pointing at this column. The hover handler uses this when the catalog is in scope. - function_
full - Render a DB-side function with signature + return type + body when
available. Body is taken from the
commentfield, where introspection stashes thepg_get_functiondef()output. - table
- table_
ddl - Synthesise a CREATE TABLE that mirrors the catalog. Columns first,
then constraints. Aligned name + type columns for readability.
Keywords are cased according to the active hover keyword case (set
by
dsl_hover::hover_with). - table_
with_ catalog - Render the table card + every catalog-wide attachment found via
cat(inbound FKs from other tables, sequences owned by this table’s columns). Used by the hover handler which has the full catalog in scope; resolver.rs (which doesn’t) keeps callingtable()for the bare card. - user_
type