Repository navigation
EP-ANALYSIS+ — Configurable code analysis & extensibility #67
Description
Epic / tracking issue. Priority P1.
Source: docs/SSDT_PARITY_BACKLOG.md §EP-ANALYSIS+. Mirrors MS rows Code analysis enable/disable GUI + run code analysis.
Today the analyzer rules are all-or-nothing. SSDT lets you enable/disable rules, set severity, and ship third-party rule packs. Add per-project config, CLI overrides, SARIF output, and an extensibility point.
Child tasks are linked below.
Child tasks
- EP-ANALYSIS+: per-rule config (.pgproj / .pgproj.analysis.json) — enabled + severity #77
- EP-ANALYSIS+: honor rule config in PgAnalyzer + CLI override (--rule PG003=off) #78
- EP-ANALYSIS+: external rule-pack extensibility (DacFx contributor model) #79
- EP-ANALYSIS+: SARIF output (analyze --format sarif) + ruleset doc page #80
- EP-ANALYSIS+: grow the rule set (naming/casing, missing PK, untyped numeric…) #81
Activity
ilijevicdenis commentedon Jun 7, 2026
EP-ANALYSIS+ deliverables are complete on
milestone/m7-ssdt-parity: per-rule config.pgproj.analysis.json(#77), CLI--rule(#78), SARIF (#80), and external rule packs (#79 —IPgRule+RulePackLoader). Two new built-in rules landed too (PG006 missing-PK, PG008 untyped-numeric). Closing the epic. #81 ("grow the rule set") stays open as a standalone, open-ended backlog for future lints — it doesn't need the epic open.docs(progress): update delivery plan — M7 6/8 epics; EP-ANALYSIS+ clo…