Evalkeeper
    Preparing search index...

    Type Alias PrismaFeedbackMap

    How Evalkeeper's feedback table maps onto an app's own thumbs table, for an app that recorded thumbs up and down before Evalkeeper. Pass it to prismaFeedbackStore (and deleteScopedRows); leave out anything named the same.

    A table without input (most thumbs tables never kept inputs) still gives the weekly summary's thumbs-down alerts and the hub's counts, which need only the rating, feature, and time; its ratings can't become cases, and whyNotACase says so.

    type PrismaFeedbackMap = {
        fields?: { evalFeedback?: FeedbackColumnMap };
        models?: { evalFeedback?: string };
        ratings?: RatingValues;
    }
    Index
    fields?: { evalFeedback?: FeedbackColumnMap }

    Column names, keyed by Evalkeeper's field (raterId: "userId"). null says the table has no such column (reason, excerpt, input, output, status, or caseId): reads give null (a status, OPEN), and writing a value fails rather than losing it.

    models?: { evalFeedback?: string }

    The table's model on the Prisma client, as the client spells it (prisma.aiFeedback is "aiFeedback").

    ratings?: RatingValues

    What your rating column holds for each, when it isn't UP and DOWN (an enum with other names, say { UP: "up", DOWN: "down" }). A value that's neither reads as a thumbs up.