MDAA TS Docs
    Preparing search index...
    interface FormFieldProps {
        description?: string;
        glossaryId?: string;
        required?: boolean;
        searchable?: ("LEXICAL" | "TECHNICAL")[];
        type:
            | "String"
            | "Boolean"
            | "Integer"
            | "Long"
            | "Float"
            | "Double"
            | "Timestamp";
    }
    Index

    Properties

    description?: string

    Human-readable description of the field, annotated via the Smithy @documentation trait. Lets stewards see what the field means when the form is attached to an asset.

    Validation: Optional; string

    - no description
    
    glossaryId?: string

    Glossary ID this field is linked to, annotated via @amazon.datazone#glossaryterm("<id>"). Makes the field filterable via the Search/SearchListings APIs. May be a literal, pre-existing glossary ID, or a deploy-time-resolved value from a declared glossaries reference; deploy-time values are not synth-time validated since their resolved value isn't known until deploy.

    Validation: Optional; valid DataZone glossary ID (unless resolved from a deploy-time glossaries reference)

    required?: boolean

    When true, the field is annotated @required and must be populated when the form is attached to an asset.

    Validation: Optional; boolean

    false
    
    searchable?: ("LEXICAL" | "TECHNICAL")[]

    Search indexing modes for the field, annotated via @amazon.datazone#searchable. LEXICAL enables stemmed/partial matches (disables semantic search); TECHNICAL indexes for technical identifier search. Omit for no explicit indexing.

    Validation: Optional; array of 'LEXICAL' | 'TECHNICAL'

    type:
        | "String"
        | "Boolean"
        | "Integer"
        | "Long"
        | "Float"
        | "Double"
        | "Timestamp"

    Smithy prelude type for the field (e.g. String, Boolean, Integer).

    Validation: Required; one of String | Boolean | Integer | Long | Float | Double | Timestamp