Skip to content

Allow config overrides of validation severity #92

Open

Description

@mindsocket

Related to #60 and #44 and #8

#60 applies to rules, this would extend to other validation types.

Concrete use case: space covering a large existing knowledge base with sparse use of types or types from other schemas. Want to validate types that are recognised but not complain about unrecognised content.

  • treat 'no-type' as 'info' instead of 'warning' or 'error'
  • treat 'type not valid' as 'info' instead of 'error'
Space Validation Results
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Content and structure
  Valid                                   81
  Schema validation errors                37
  Broken links                             0
  Duplicate keys                           0
  Rule violations                          0
  Hierarchy violations                     0
  Orphans (hierarchy nodes - no parent)    0
  Excluded during parsing                2286

...

   foo/bar.md: warning - no-type - No front-matter or type specified

...

Schema validation errors:

   foo/baz.md:
      type: "opportunity" is not valid. Allowed: "concept", "entity", "index", "note", "source", "synthesis"

Activity

  1. mindsocket commented on Oct 14, 2026

    @mindsocket
    OwnerAuthor

    Update from semantic rules (#114, PR #151): rule severity is now a shape a config override has to fit.

    • severity on a rule is a level (error/warning/info), or, on semantic rules, a map of verdict to error|warning|info|ignore. ignore means the rule ran and the verdict is recorded but not reported.
    • A rule with no severity takes its category default (validation=error, coherence/workflow=warning, best-practice=info).
    • Gating follows the reported severity per verdict.

    Design implication for this issue: an override should address the same unit, i.e. rule id, optionally verdict, mapping to a level or ignore. Not built in #151; the map was shaped so a config-level override can merge onto it. Disabling a rule (don't run) and ignoring (run, discard) are separate features and probably separate keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions