Why this matters
Surfaces every parse error from libpg-query as a single lint diagnostic. Without this rule the plugin would silently skip un-parseable files, which is exactly the case where a human reader needs the loudest possible signal.
Examples
Incorrect
-- typo: should be SELECT
INVALID_KEYWORD * FROM users;SELECT * FROM WHERE id = 1;Correct
SELECT * FROM users WHERE id = 1;Configure it
// eslint.config.js
import postgresql from "eslint-plugin-postgresql";
export default [
{
files: ["**/*.sql"],
languageOptions: {
parser: postgresql.configs.recommended.languageOptions.parser,
},
plugins: { postgresql },
rules: {
"postgresql/no-syntax-error": "error",
},
},
]; Options
Edit the SQL — only no-syntax-error is enabled.
Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.
Diagnostics
No issues found.
1 rule enabled.
Rule under test
no-syntax-error — plus no-syntax-error as a safety net.