Evalkeeper
    Preparing search index...

    Type Alias AnswerEditorProps

    What an app's own answer editor gets, for answers plain fields can't edit well (a list of facts with a category each, a verdict with reasons). The editor is a client component that renders its own controls and keeps the whole answer, as JSON, in a form field named name (a hidden input). Register it in your wiring module's answerEditors, keyed by suite; the copied answer key, "Add a case", and blind rating use it in place of the suite's answer fields, and the actions check what it submits against the suite's labelValue.

    type AnswerEditorProps = {
        fields: readonly FormField[];
        idPrefix: string;
        input: unknown;
        name: string;
        value: unknown;
    }
    Index
    fields: readonly FormField[]

    The suite's answer fields, for their labels and help.

    idPrefix: string

    Prefix for element ids, unique on the page.

    input: unknown

    The case's input, when there is one yet (null on "Add a case").

    name: string

    The form field to submit the answer under, as JSON.

    value: unknown

    The current answer, or null for a new one.