Hi Ryan, > If this is the intended behavior, the separator in ChoiceField should > be removed. Is that the intention?
Yes. > Is the parameters array a > nearly-dead feature that should be killed off? If so, this would put > the separator into ChoiceField. Is that more correct? It's nearly dead, but I think it has a valid purpose. Through this array, the rendering of a field can be customized in the template. E.g., a template designer can change the separator of a field without consulting a developer. Ideally, all options that affect the rendering of a field would be passed through this array. Unfortunately that's not possible, because often a change in the rendering affects the how the submitted and bound data is processed (e.g. the option "widget" in DateField). What's your opinion on the best solution here? > It would be useful on ChoiceField > subclasses such as CountryField. Can you explain why? > Additionally, the behavior of > getEmptyValue() only returns a value if the field is *not* required. This should be changed. getEmptyValue() should return the value of the option, no matter whether required or not. Bernhard -- Software Architect & Engineer Blog: http://webmozarts.com Twitter: http://twitter.com/webmozart -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
