Qodana baseline suppression gaps when inspection profiles gain new checks
Baseline behavior under profile evolution Qodana baselines store suppressed issue fingerprints keyed to specific inspection IDs. When a team updates qodana.yaml to enable additional inspections — or syncs a revised IDE profile — the existing baseline file contains no entries for the newly activated inspection IDs. Consequently, code patterns that were previo
qodana