Skip to content

Dashboard: Fallback/default inputs #4101

@Draykee

Description

@Draykee

Is your feature request related to a problem? Please describe.
I'm started migrating a complex project to the new Dashboard. When editing a variant in the new dashboard, some form fields are not rendered correctly. This seems to happen when the UI configuration for that variant hasn’t been fully migrated to the new dashboard system yet. As a result, certain inputs either don’t appear or appear in an unusable state, which slows down the migration process and makes it harder to work with older configurations. This doesn't just apply to the variant page, but I assume to every custom field.

Describe the solution you'd like
I’d like the dashboard to automatically render fallback or default form inputs whenever the UI configuration for a field is missing, outdated, or incompatible with the new dashboard system. This ensures that all fields remain editable, even if the configuration hasn’t been updated yet. It would make the migration process smoother, faster, and less error‑prone.

So in case of this configuration:

{
            name: 'weight',
            type: 'int',
            defaultValue: 0,
            nullable: false,
            min: 0,
            step: 1,
            public: true,
            label: [{ languageCode: LanguageCode.en, value: 'Weight' }],
            // number-form-input only exists in angular UI
            ui: { component: 'number-form-input', suffix: 'g' }, 
}

It would just render a number input, since the type is int, in case number-form-input is not found. An additional warning in the console would be helpfull as well.

Describe alternatives you've considered

  • Manually updating or removing all UI configurations before using the new dashboard. This works but is time‑consuming and blocks incremental migration.

Additional context

  • No input visible:
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions