#606 √ resolved
Clemens Kofler

Inconsistent functionality in date_helper.rb

Reported by Clemens Kofler | July 12th, 2008 @ 08:51 PM | in 2.2

I was working on some doc patches for the date/datetime helpers when I found out that there are some inconsistencies. IMO, all date helpers (both, object related and standard ones) should support the same options to define separators. This applies for all compound helpers - i.e. date/datetime/time_select and select_date/datetime/time.

Code examples: 

# standard:
select_date(date, :date_separator => ' / ') # should work, but doesn't
select_datetime(date, :date_separator => ' / ') # should work AND is documented, but doesn't work
select_datetime(date, :datetime_separator => ' , ') # works, but isn't documented
select_datetime(date, :time_separator => ' - ') # should work, but doesn't
select_time(time, :time_separator => ' - ') # works

# object related:
date_select(object, method, :date_separator => ' / ') # should work, but doesn't
datetime_select(object, method, :datetime_separator => ' , ', :date_separator => ' / ', :time_separator => ' - ') # should work, but doesn't
time_select(object, method, :time_separator => ' - ') # should work, but doesn't

It's nothing big and it seems it's hardly ever used (otherwise, someone would have complained already) but I think it should be fixed nevertheless because it makes the date helper API inconsistent.

I've attached the failing tests for now and I'll try to come up with a patch in a day or two.

Comments and changes to this ticket

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Source available from github

The Git repository resides at http://github.com/rails

Check out the current development trunk (Edge Rails) with:

git clone git://github.com/rails/rails.git

Creating or reviewing a patch

See the contributor guide.

Creating a feature request

Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.

Creating a bug report

When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.

Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".

Shared Ticket Bins

People watching this ticket

Attachments

Tags