Skip to content

DBInput: Evaluate message property structure #4791

@mfranzke

Description

@mfranzke

A colleague suggested to evaluate our way of designing the "API" of how to control the infotext within input (we're currently using three prefixed properties) by providing the possibility to pass an object for that component instead.

I would even go as far as suggesting to allow passing an config object with most Props (except semantic and id) for the DBInfotext component

#4629 (comment)

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions