First-party VS Code integration for sqlshield —
a schema-aware static linter for raw SQL embedded in .py, .rs, and .sql
files.
Platform-specific builds of this extension bundle the sqlshield-lsp
binary, so installing the extension is enough on Linux x64/arm64,
macOS, and Windows x64/arm64. On unsupported platforms (or for users
who'd rather use their own build), install the binary manually:
cargo install sqlshield-lspIf sqlshield-lsp is not on PATH and the bundled binary isn't being
picked up, set sqlshield.serverPath to the absolute path.
The extension spawns sqlshield-lsp over stdio and forwards diagnostics
to the editor as you type. Configuration comes from two sources, with
editor settings winning per-field:
- The
sqlshield.*VS Code settings below. - A
.sqlshield.tomldiscovered by walking up from the workspace root.
- sqlshield: Restart Language Server — restart the server without reloading the window. Useful after switching the binary path.
sqlshield.schema— path to the schema SQL file (relative to workspace root or absolute). Overridesschemain.sqlshield.toml.sqlshield.dialect— SQL dialect (postgres,mysql,sqlite,mssql,snowflake,bigquery,redshift,clickhouse,duckdb,hive,ansi,generic). Overridesdialectin.sqlshield.toml.sqlshield.serverPath— binary path. Leave blank for the bundled binary; falls back tosqlshield-lsponPATH.sqlshield.trace.server— log LSP traffic for debugging.