Issue Bug Closed

#98055prototypeName defined in form yaml does not have an effect any more

Helmut Hummel 07/29/22, 13:03 updated 07/29/22, 14:00

Description

With 11.5.13 setting the prototypeName in a form definition has not effect any more.

Prerequisite
When setting this in a form definition:

type: Form
identifier: foo
label: 'Foo form'
prototypeName: fooPrototype

Expectation
I would expect to have the prototype “fooPrototype” to be selected when rendering the form
and no other prototype has been passed.

Actual result:
What actually happens is, that the “standard” prototype is selected.

Analysis

This is due to the new FormRequestHandler class, which already sets the prototype to standard,
if it is not passed into the view helper, instead of allowing it to be null until the form definition is loaded

Reviews 1