Settings & Suppression

beginner concepts

Settings & Suppression

The Settings window is the central place to configure check severity, enable / disable rules, suppress findings with an audit trail, tune Health Score thresholds, and toggle integrations.

Open it from Window > Kronnect > Editor Doctor Pro > Settings.

Tabs

Tab	What you do here
Rules	Per-rule severity override and enable / disable toggle. Search by id or title; filter by module.
Suppressions	The suppression store: every per-issue, per-rule and per-scope ignore the project carries, with author / date / reason / expiry. Expired entries are highlighted.
Health Score	Per-severity penalty weights and the optional baseline file path.
Safe Delete	Protection rules (paths or check ids that should never produce candidates) and the Trash size indicator.
Conventions	Tag contracts, closed-tag list, the STRAY check confidence threshold and minimum sample size, and the Custom Rules editor (see Custom Rules).
Integrations	Enable / disable the Scene Pilot Pro bridge; install / remove the Cecil package.
Scopes	Demo folders skip toggle (default off) and include / exclude defaults applied to every scan.

Rule overrides

Every check ships with a default severity (Info, Warn, Error, Critical) and a default enabled / disabled state. Style and convention rules ship disabled by default so they don't drown the signal on first run; performance, lifecycle and asset-health rules ship enabled.

From the Rules tab you can:

Disable any rule. Disabled rules don't run, don't appear in the Doctor, and don't count toward the Health Score.
Override the severity of any rule. The override is project-local (under ProjectSettings/EditorDoctorPro/) and shared via git.
Reset a rule to its shipped defaults via the per-row menu.

Suppressions

Suppressions silence findings without disabling the rule globally. Three scopes:

Per-issue - silence one specific finding, identified by its stable fingerprint (check id + asset GUID + sub-target).
Per-rule - silence every finding from a given check, project-wide.
Per-scope - silence findings from a given check on assets matching a path glob (e.g. EDP-CODE-CONV-PUBLIC-FIELD-IN-MONOBEHAVIOUR on Assets/Plugins/**).

Every suppression entry carries:

Author	`System.Environment.UserName` when the suppression was created.
Date	UTC ISO 8601 of creation.
Reason	Optional one-line note. Recommended for review-time context.
Expiry	Optional date after which the entry is highlighted as expired and the suppressed findings reappear.

The suppression store lives at ProjectSettings/EditorDoctorPro/suppressions.json and is shared via git so your team sees the same suppressions.

Workflow: When you suppress something, write a one-line reason and set an expiry of 90 days. When the entry expires, EDP highlights it and you re-review. This stops the suppression list from rotting silently.

Health Score thresholds

The Health Score is a 0-100 integer per module plus a project-wide aggregate. Penalties per finding are configurable:

Severity	Default penalty
Critical	20
Error	5
Warn	1
Info	0

The per-module score is max(0, 100 - sum(penalty)). The project aggregate is the average across modules. See Reports & Health Score for baseline storage.

Protection rules

Under the Safe Delete tab you can register paths that should never become candidates regardless of reachability. Default protections include common paths like Assets/Editor Default Resources/; you can add your own with a path glob and an optional reason.

Demo folders

EDP skips folders named Demo/ or Demos/ from every scan by default. Most projects pull demos from imported Asset Store packages where you can't act on findings; including them just inflates the report. Asset publishers dogfooding their own demos can flip the toggle on so EDP audits the demo content they ship.

Was this page helpful? |

Settings & Suppression