@mermaid-lint/core
    Preparing search index...

    Interface ValidationError

    A syntax error from diagram validation, with an optional location relative to the diagram body.

    interface ValidationError {
        col?: number;
        line?: number;
        message: string;
        structural?: boolean;
    }
    Index

    Properties

    col?: number

    1-indexed column within the diagram body, when known.

    line?: number

    1-indexed line within the diagram body, when known.

    message: string

    Human-readable error message.

    Any line number mermaid quotes inside this text is body-relative, matching ValidationError.line. blockToDiagnostics maps both when it builds a Diagnostic; code calling validateBlock directly and printing this beside a file position should do the same.

    structural?: boolean

    True when the error is a defect in the document rather than the diagram — an unclosed fence or an empty block — so no diagram was ever parsed.

    Suppression directives deliberately do not apply to these. An unclosed fence has no parseable body (its body is the __UNCLOSED_FENCE__ sentinel), so no in-diagram %% directive can reach it and a -disable-file mermaid would be the only lever — a blunt one that would hide a broken fence indefinitely. Suppressing "mermaid rejected this diagram" should not also suppress "your Markdown never closed".