Skip to content

Validate filter_form explicitly in list action configuration #51

Description

@javihgil

Problem

list action configuration allows filter_form to stay null, but the runtime flow assumes a valid form type is always present when building the list filter form.

Current behavior

  • ListActionConfiguration defines filter_form as optional.
  • ListActionHelper::createFilterForm() calls the form factory with the resolved type directly.
  • If filter_form is missing or invalid, the failure happens later at runtime instead of during configuration processing.

Why it matters

This makes controller configuration errors harder to detect and produces a less helpful failure mode. The package should fail early during action configuration, not only when the list action is executed.

Suggested direction

Require filter_form for list actions, or make the runtime flow handle its absence explicitly and consistently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions