Martijn Vos

I understand. I'll submit a patch there.

Even so, isn't it dangerous for Rails to blindly assume that it receives a class of a specific type when that clearly isn't automatically true? A respond_to? ch...

This fix can also be found in http://github.com/mcv/rails/comm...

Here's the patch.

For some reason, I don't quite understand why, does

<%= f.date_select :card_expires_on, :discard_day => true, :start_year => Date.today.year, :end_year => (Dat...

Another minor but ugly issue that remains is that when I use the "year" select box, it starts at dates in the distant past. I want those to be available, but th...

This patch fixes the problem. For me at least -- it's likely there are use cases I'm not aware of.

The patch doesn't add or update any tests because I couldn't ...

When using date_select, it's possible for the user to submit only month and day, leaving year empty. How to handle that issue is up to the developer of the site...

add_prompts_to_date_helpers_2.3.0.diff doesn't entirely fix this issue when applied to 2.2.2. It still uses today as default value instead of nil.

In date_helpe...

+1

Why exactly is this stale, and not already in Rails?

Also +1 on doing something similar for class name, although I think that should be a separate ticket.