Skip to content

validate should support baselines and severity filters for known findings #3008

Description

@Widthdom

Found while dogfooding the locally built cdidx.

Evidence

validate --json currently reports known U+FFFD source literals in test and source fixtures as severity: info. During repeated audits, these known findings add noise.

Expected

validate should support a baseline file and/or filters such as --severity warning|error and --kind replacement_char so known informational findings can be managed explicitly.

Duplicate check

Searched open issues for validate replacement character baseline severity filter U+FFFD; no clear duplicate found.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions