@vivantel/virage-core
    Preparing search index...

    Interface ChunkerEntry

    Wraps a FileChunker with fileSet-level metadata and pipeline-level path filters. One ChunkerEntry is created per (fileSet × chunkerConfig) pair during config load. include and ignore are the fileSet's patterns; they are applied by the GitTracker and ChunkProcessor before routing files to the chunker. fileSetTags and tagRules drive the tag pipeline (ADR-043, ADR-046).

    interface ChunkerEntry {
        chunker: FileChunker;
        chunkerKey: string;
        fileSetName: string;
        fileSetTags: string[];
        ignore?: string[];
        include?: string[];
        tagRules: TagRule[];
        templates?: ChunkerTemplate;
    }
    Index
    chunker chunkerKey fileSetName fileSetTags ignore? include? tagRules templates?
    chunker: FileChunker
    chunkerKey: string

    The npm package name of the chunker — stored as ChunkMeta.chunkerKey (ADR-044).

    fileSetName: string

    Name of the fileSet this entry belongs to.

    fileSetTags: string[]

    Pre-computed from fileSet.tags — injected into every chunk from this fileSet.

    ignore?: string[]

    If set, files matching any of these globs are skipped for this chunker.

    include?: string[]

    If set, only files matching at least one of these globs are sent to this chunker.

    tagRules: TagRule[]

    fileSet.tagRules — applied per-file based on minimatch glob matching.

    templates?: ChunkerTemplate

    Per-chunker output templates (ADR-045). No-op until renderer ships.

    Settings
    Member Visibility

    On This Page
    Properties