Form\Factory can handle config with null elements

[bacinsky]

There is an use case, when I have configured form with elements, but I want to disable some elements later in the config of the other module. So I override it with null, but the Form\Factory doesn't recognize it, so it needs a little fix.

[grizzm0]

Why don't you simply use $form->remove('baz'); instead of setting the element to null?

    /**
     * Remove a named element or fieldset
     *
     * @param  string $elementOrFieldset
     * @return FieldsetInterface
     */
    public function remove($elementOrFieldset)
    {
        if (!$this->has($elementOrFieldset)) {
            return $this;
        }

        $entry = $this->byName[$elementOrFieldset];
        unset($this->byName[$elementOrFieldset]);

        $this->iterator->remove($entry);

        if ($entry instanceof FieldsetInterface) {
            unset($this->fieldsets[$elementOrFieldset]);
            return $this;
        }

        unset($this->elements[$elementOrFieldset]);
        return $this;
    }

[bacinsky]

@grizzm0 Hi, you don't understand. I don't even want to add it. It's about merging configs and creating the form without accessing its instance.

I want to disable some elements later in the config of the other module.

That means statically, not runtime.

[ezimuel]

@bacinsky can you provide an example for that scenario? Why you want to set a form element to null?

[bacinsky]

@ezimuel I already wrote it. Imagine you have a module with configuration for the form. That form has some elements (maybe only one) I don't want to use in some applications, so I override the config with the null for that element, because it can't be removed by merge. I think this is easy to understand, maybe my bad English cause misunderstanding.