lint-project
Runs project-scoped structural lint rules against an index -- checks such as god-class, unused-public-symbol.
Read this when you want architecture-level findings that need the whole project, such as god-class, circular-uses, unused-public-symbol or layering-violation, rather than per-file diagnostics. It runs those project-scoped rules against an index.
How to run it
Full flag list: lint-project in the CLI reference.
Flags
| Flag | Argument | Meaning | Default |
|---|---|---|---|
--db | <file.sqlite> | ||
--rule | |||
--layers | <f.json> | ||
--json |
Where to click
- RAD Studio main menu: drag-lint > Code Quality > Project Structure Rules (god-class, layering...)...
Needs: index
Details
Runs project-scoped structural lint rules against an index -- checks such as god-class, unused-public-symbol, circular-uses and layering-violation that need whole-project context rather than a single file. Reach for it for cross-file architectural findings, not per-file diagnostics.
Running it from the CLI
drag-lint lint-project --db <file.sqlite> [--rule god-class|unused-public-symbol|interface-reference-cycle|layering-violation|unused-private-member|unused-unit-in-uses|circular-uses|repeated-type-switch|global-only-uses-edge|duplicate-global-decl|uses-global-census|discarded-effect-free-result|query-name-with-effect|assert-with-side-effect] [--layers <f.json>] [--json]Reaching it in the IDE
No IDE surface -- this is a CLI-only feature.
What it needs
An index IS required. The project's DB lives at
<project folder>\_D-RAG\<project file>.sqlite; run
drag-lint resolve-dbs --project <X.dproj> if unsure.
Example
Illustrative only:
drag-lint lint-project --db C:\Projects\MyApp\_D-RAG\MyApp.sqlite --rule circular-uses --jsonThis would report circular-uses findings for MyApp as JSON.