Actually you will not have a default value even if you set 'required' = true

What do you mean with an entry for the empty value? So far, the behavior looks OK for me, not a bug.

@bschussek ping

@klaussilveira There should be a radio button like this:

(o) Empty

where "Empty" corresponds to the value of the "empty_value" option.

So where are we with this?

if i have a entity field with expanded set to true, and required to false, even adding empty_value manually does not give me the empty ("no selection") radio. Which means if the use accidentally selects he cannot unselect or select a blank option anymore.

This is critical bug, 2.1 should at least get an option where explicitly setting empty value makes it show up.

This is not solved yet. I tried to solve it once and I remember that it was not easy.

If you need a quick solution, I'd hardcode an empty radio button in your Twig template.

@bschussek it seems to me that in the case of expanded = true and required = false with multiple = false the empty value should be parsed. However right now the hardcode index in the ChoiceType checks f ($options['multiple'] || $options['expanded']) { which is an invalid check.

Fixing this and adding the same empty value handling in the field definitions should get us a empty radio. Or am overlooking some core aspect of this?

@rdohms Yes, you are overlooking that the way that the options are generated for expanded fields works completely differently than for collapsed field. The check you are quoting is a safeguard because (even if the check is changed) it won't work anyway.

Any news on this?

Fixed in the referenced PR.

Maybe I misunderstood the usage of the radio button in my use case:

        $builder
            ->add('windowMaterialId', 'entity', array(
                'class' => 'Acme\AppBundle\Entity\WindowMaterial',
                'expanded' => true,
                'required' => true,
            ))
        :

This will render two choices with the values 0 and 1.

In this case I want only two buttons - the ones with the choices. But I don't want any choice pre-selected and I don't want an additional "Please Choose" choice.

I tried several variations with the empty_* parameters without succes.

Is this not possible or a wrong usage for a radio button - do you recommend a simple select then?
Just wondering because many forms simply have a yes/no choice with radio buttons which are no pre-selected.

@webdevilopers the rpe-selected choice will be set based on the data in the object bound to the form. If the property windowMaterialId in it does not contain one of your WindowMaterial, there will be no pre-selected element.

On a side note, naming the property windowMaterialId when it contains a WindowMaterial instance is weird. the property does not contain an id.

Thanks @stof . I am refactoring a legacy form and yet I couldn't change the naming in production! ;)

Indeed when I started again on the form this morning I no longer experienced the mentioned pre-selection.

The only thing I recognized is that setting 'required' => false will add the extra None option which is an expected behaviour as far as I understood.