Expand description
Structured findings: severity, entity, rule, message.
A validation result must be machine-readable so a downstream consumer can act on it and a CI gate can fail on it.
§Internal split
finding.rs: severity and the individual finding.detail.rs: typed detail behind a finding’s message.path.rs: entity and attribute paths, and their total order.summary.rs: counts and the assembled report.
Structs§
- Catalog
Member Detail - A member of a catalog set that disagrees with the catalog’s template.
- Finding
- One thing a validator has to say about a file.
- Report
- Everything a validation run produced.
- Reserved
SetName - A set name using a reserved prefix the catalog does not define.
- Rule
Detail - One EXPRESS rule result.
- Summary
- Counts by severity, for a one-line verdict.
Enums§
- Budget
Exceeded - Which limit stopped an evaluation.
- Catalog
Mismatch - How a set or member disagrees with its catalog template.
- Finding
Detail - Structured detail of a finding, when its check provides one.
- NotEvaluated
- Why a rule was not evaluated.
- Path
- Where in the file a finding applies.
- Rule
Outcome - What evaluating a rule on one instance, value or file concluded.
- Rule
Scope - The declaration holding a rule.
- Severity
- How serious a finding is.