{"id":2643,"date":"2012-10-22T13:48:24","date_gmt":"2012-10-22T10:48:24","guid":{"rendered":"http:\/\/railsware.com\/blog\/?p=2643"},"modified":"2021-08-16T15:26:47","modified_gmt":"2021-08-16T12:26:47","slug":"rails-4-0-activesupport-small-improvement","status":"publish","type":"post","link":"https:\/\/railsware.com\/blog\/rails-4-0-activesupport-small-improvement\/","title":{"rendered":"Rails 4.0 ActiveSupport small improvement"},"content":{"rendered":"\n

A few days ago my patch with the beginning_of_week<\/code> config option has been merged to Rails master, so starting from Rails 4.0 we’ll gain full control over the week start day.
<\/p>\n\n\n\n

Preface<\/h3>\n\n\n\n

Working on Interstellar, I’ve found out that
ActiveSupport has a lot of useful methods like Date#beginning_of_week<\/code>, Date#end_of_week<\/code> and many others.
However, there was a small thing that was quite a bit annoying:
all those API methods were tied to Monday as the first day of a week.
Not a big deal while developing web applications<\/a> targeted to European market, but working on a US oriented stuff it might be useful to set Sunday as the beginning of a week.
Sure, you can fix this in a couple of methods… But hey, we are open source community, right?<\/p>\n\n\n\n

We can patch it up baby…<\/h3>\n\n\n\n
\"Ruby<\/a><\/figure><\/div>\n\n\n\n


The first patch<\/a> I come up with was an extension that makes possible to pass week start to beginning_of_week<\/code> and end_of_week<\/code> methods. It was accepted and merged into Rails 3.2 relatively fast.<\/p>\n\n\n\n

And all was great, but there was another bunch of cool API methods: next_week<\/code> and prev_week<\/code>.
They already have a single argument: a day in next (previous) week. That said, we cannot pass week start as an argument to these guys.
One of the possible solutions was an application wide config option for the week start.
In this case, we can use beginning_of_week<\/code> inside next_week<\/code> and prev_week<\/code> without having to pass the start of the week manually.
So I hit another pull request with the beginning_of_week<\/code> config option.
It took more than 6 months to get this merged, and now I’m happy as I can be.
Since Rails 4.0 we’ll get full access to ActiveSupport calendaring API.<\/p>\n\n\n\n

Examples:<\/p>\n\n\n\n

    \nTime.now.beginning_of_week.to_date          #=> Mon, 22 Oct 2012\nTime.now.beginning_of_week(:sunday).to_date #=> Sun, 21 Oct 2012\nDate.beginning_of_week = :thursday\nTime.now.next_week.to_date                  #=> Thu, 25 Oct 2012\n<\/pre>\n\n\n\n
Instead of epilogue<\/h3>\n\n\n\n
There’s a lot of stuff out there that still should be improved.
For example, `Date` now knows too much about `Week`. Begging for a separate class (as Jeremy stated<\/a>).<\/p>\n\n\n\n
Another thing is that Rails stores week days in a different way than Ruby:<\/p>\n\n\n\n
Date::DAYS_INTO_WEEK[:monday] #=> 0\nTime.now.monday.wday #=> 1 (because Ruby stores Sunday as zero week day)\n<\/pre>\n\n\n\n
It’s time to contribute, so go for it!<\/p>\n","protected":false},"excerpt":{"rendered":"
A few days ago my patch with the beginning_of_week config option has been merged to Rails master, so starting from Rails 4.0 we’ll gain full control over the week start day. Preface Working on Interstellar, I’ve found out thatActiveSupport has a lot of useful methods like Date#beginning_of_week, Date#end_of_week and many others.However, there was a small…<\/p>\n","protected":false},"author":34,"featured_media":2854,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Innokenty Mihailov"],"class_list":["post-2643","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"categories_data":[{"name":"Engineering","link":"https:\/\/railsware.com\/blog?category=development"}],"post_thumbnails":"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2012\/10\/elvis_patch_it_up.gif","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/2643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/comments?post=2643"}],"version-history":[{"count":35,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/2643\/revisions"}],"predecessor-version":[{"id":14130,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/2643\/revisions\/14130"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media\/2854"}],"wp:attachment":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media?parent=2643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/categories?post=2643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/tags?post=2643"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/coauthors?post=2643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}