|
Welcome to This week in Rails, your weekly inside scoop of interesting commits, pull requests and more from Rails.
As you might recall, we have been assembling a team of editors for this newsletter. I am very excited to introduce our first editor Kasper Timm Hansen who has helped prepare today's newsletter for you!
(If that's something you might be interested in doing, let me know!)
I'll let Kasper take it from here.
|
|
|
|
|
Thanks to the 24 contributors who helped making Rails better this week. You can almost smell that first release candidate for Rails 4.2 now. Go ahead, rip yourself a new nostril!
|
|
|
|
|
Active Job is coming in Rails 4.2. That smooth wrapper around common queuing libraries just won't gel unless you've got a way to test it. While you've been able to test your jobs, you haven't been able to read about it in the testing guides. Fret no more, there's a new section covering asserting your jobs are on queue and that they do what you expect.
|
|
|
|
|
PostgreSQL party people: in Rails 4.2, Active Record will require at least version 0.15 of the pg gem. This has better concurrency on MRI. You want this performance in your concurrent MRI app, yes? Add the requirement to your Gemfile too.
|
|
|
|
|
For historical reasons, rake test only ran a subset of the test cases in the test folder. To actually run all tests, you'd need to use rake test:all. In Rails 4.2 there can be only one. So rake test now runs every test.
|
|
|
|
|
In between Rails 4.2 beta 2 and 4 a regression that slowed speed of test runs slipped in. Luckily, this contributor has a tender passion for sweet cachin'. The fix: cache the table for your visitors, dingus!
|
|
|
|
|
With more real-world apps taking part in the beta testing, the Rails team has been able to identify and address some performance regressions.
This commit addressed a problem in Active Record with time conversion.
|
|
|
|
|
Ruby is back to slam dunk another security release straight into your heart. To avoid any insecurity (in deployments or life) we recommend upgrading as soon as you can.
May your markup always be extensible and let it never Deny us its Service when we expand it.
|
|
Wrapping up
And that's a wrap for this issue of This week in Rails. As always, Rails changes faster than what we can cover here, so do take a look for yourself.
Thanks for reading, everyone!
This is Kasper signing off.
This Week in Rails is completely devoid of newsletter enhancing performance drugs. As such it's safe to share with all your Rails friends!
P.S. Well, a tiny amount of mostly insignificant animals were slightly "dented" during the making of this newsletter. Please advise.
|
|
|
|
