On Sep 16, 5:14 am, "Tim Haines" <[EMAIL PROTECTED]> wrote: > Opposite is useful for when someone wants the option to unselect an already > selected date and return the value to nil. Or, you want today to be the > default, but give the user the choice to select nil. i.e. When are you > going to do this low priority task?
Right, good examples. I can't think of any reason we shouldn't change this -- I can't think of any reason a developer would want to explicitly specify a default and have it be ignored. The fix is pretty simple -- here's my monkeypatch: http://pastie.org/273313 -- I'm just adding a check for the absence of the :default option to the return statement at the top of the default_datetime method. Shouldn't break any existing behavior. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
