@theredhead — Frontend Library - v1.0.0
    Preparing search index...

    Dynamically generates text columns from a datasource row's properties.

    This component automatically introspects the first available row and creates a UITextColumn for each property (key). This eliminates the need to manually declare columns when you want to show all properties with basic text rendering.

    Properties are sorted alphabetically for consistent column ordering.

    <!-- Instead of declaring columns manually -->
    <ui-table-view [datasource]="adapter">
    <ui-text-column key="name" headerText="Name"></ui-text-column>
    <ui-text-column key="email" headerText="Email"></ui-text-column>
    <ui-text-column key="age" headerText="Age"></ui-text-column>
    </ui-table-view>

    <!-- Use auto-generation -->
    <ui-table-view [datasource]="adapter" uiAutogenerateColumns></ui-table-view>
    Index

    Constructors

    Properties

    excludeKeys: InputSignal<string[]> = ...

    Properties to skip when generating columns. Useful for filtering out internal or metadata properties.

    excludeKeys: ['id', '_internal', 'metadata']
    
    generatedColumns: Signal<{ headerText: string; key: string }[]> = ...
    headerMap: InputSignal<Record<string, string>> = ...

    Custom header text mapping. When a property key matches an entry, that custom text is used instead of the property key (or humanized version).

    headerMap: { firstName: 'Given Name', lastName: 'Family Name' }
    
    humanizeHeaders: InputSignal<boolean> = ...

    Whether to use humanized header text (space-separated, title-cased). Defaults to true.

    Property "firstName" becomes "First Name"
    
    row: InputSignal<Record<string, unknown> | null> = ...

    The row data to introspect. This is typically a signal that emits the first available row from your datasource.

    If no row is provided, no columns will be generated.