data-cap
    Preparing search index...

    Interface RawCreateDataCall

    One buildData(...)/createData(...) call found in a file's top-level statements.

    interface RawCreateDataCall {
        declarationPosition: SourcePosition;
        exportName: string | undefined;
        fieldPositions: Readonly<Record<string, SourcePosition>> | undefined;
        fieldsRef: SchemaRef;
        kind: "buildData" | "createData";
        node: CallExpression;
        operationNames: OperationNames | undefined;
        operationPresence: OperationPresenceByKind | undefined;
        operationWrites: OperationWritesByKind | undefined;
    }
    Index
    declarationPosition: SourcePosition

    Position of this call's own declaration site -- always available, since node always resolves to a real AST location regardless of how fields itself resolves.

    exportName: string | undefined

    The exported binding name (export const X = buildData(...)), or undefined if unexported -- see the accompanying warning in that case.

    fieldPositions: Readonly<Record<string, SourcePosition>> | undefined

    Position of each top-level field's own key, keyed by field name -- only when fieldsRef.kind === "literal" (an identifier-resolved fields crosses a file boundary this pass doesn't retain AST access to; undefined there, never guessed at).

    fieldsRef: SchemaRef

    How this call's fields argument resolves within this one file.

    kind: "buildData" | "createData"

    "buildData" or "createData" -- which call form this is.

    node: CallExpression

    The full call expression AST node, for later structural inspection.

    operationNames: OperationNames | undefined

    Static getter/mutator/subscription names, or undefined for a buildData() call.

    operationPresence: OperationPresenceByKind | undefined

    Static processor/optimistic key-presence facts, keyed the same way as operationNames. undefined for a buildData() call, which has no operations section.

    operationWrites: OperationWritesByKind | undefined

    Static writes field-ownership shapes, keyed the same way as operationNames. undefined for a buildData() call, which has no operations section.