There are often times when populating the "default" values of a form, where I may be passing in a php boolean true/false value, and currently the sfForm framework cannot parse this correctly.
For example, I when you have a field in doctrine that is defined as a boolean, it will return php type true or false, as the value of that field, regardless of if it is stored in the db as 1 or 0. However, if I have a radio button or check box widget that is technically a boolean, it should recognize if I pass a php type true/ false into the default value for that tag and properly type cast this to an integer, 1 or 0 respectively. An HTML form can never hold a php boolean value, so I don't see how this would ever harm anything. I took a look at the code, and there are several possible place where this check/conversion could take place, but I think its up to you, Fabien, to decide where this should go. I would assume it would be best coverted just before HTML output. Thoughts? --Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
