This week in Rails

Issue #8

Welcome to This week in Rails, your weekly inside scoop of interesting commits, pull requests and more from Rails.

Featured

Test-induced design damage

DHH elaborating on the topic of how TDD might encourage over-abstraction by making "easy to test" one of the top priorities.

DHH Code Ping Pong #3

I missed this one due to the all the RailsConf stuff, but the third (out of the five) DHH code ping pong has been posted. This time the crowd's decision seems pretty much unanimous!

This week's top contributors

This week's top contributors include @rafaelfranca, @tenderlove and @eileencodes. Please join me in thanking the 32 awesome people who dedicated their time this week to help improve the framework we love <3 <3 <3

Save the date for RailsConf 2015

RailsConf 2015 is happening in Atlanta from April 21-23. This time it is going to be a 3 days, 4 track conference. As always, follow @railsconf to stay in the loop.

Fixed

"...while Mac OS X users can use Tokaido"

This also got lost last week, but Tokaido 1.0 is here!

Edge Rails now requires `arel` master

Rails now depends on the master branch of arel after adequaterecord is merged. If you are starting a new edge Rails application, be sure to add gem 'arel', github: 'rails/rails' to your Gemfile.

Breaking up complex conditionals in Active Record

While fixing some other bugs inside Active Record, @eileencodes took the time to refactor out some complexity in the relevant parts of the codebase as well.

Ensure statements are closed after queries in SQLite3

@timuralp poured an awesome amount of quality research into fixing this issue, read the discussion thread and the original issue for all the juicy details.

Separate translations for plural error messages

When translating validation error messages (such as length validation), you can now supply a different translation for the singular and plural context.

Wrapping up

And that's it for this issue of This week in Rails. As always, there are a lot more interesting things happening on Rails than I can cover here, so I encourage you to check them out!

If you have any feedback for me, please feel free to email me or let me know on twitter!

Thank you for reading! <3 <3 <3

P.S. If you liked what you read, please share this newsletter with your Rails friends!