Matt Jones wrote: > Essentially, anything that isn't blank and isn't "true-y" (see the > list in the source) gets mapped to false. > > About the only way I can think of to avoid this is to override the > accessors for those variables and map everything that isn't true to > nil. > > --Matt Jones
Thanks Matt, In the relative scheme of things it works in the way it should. If someone places a boolean value of true it is indeed true. If someone places a boolean value of false it is indeed false. If someone leaves it empty, it will validate incorrectly and the message will be displayed. So, overall, it's working fine. If, however, someone places some strange value that is not true or false it also returns false. I'm fine with that as it is highly unlikely that someone would do such a thing and if they do, it returns the expected behavior, only it does not send them the message. -- Posted via http://www.ruby-forum.com/.
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
