Welcome to the forth issue of This week in Rails, your weekly inside scoop of interesting commits, pull requests and more from Rails.
It turns out that some of the items from last week were linking back to the wrong content. My apologies! I have included the "fixed" version at the bottom of this week's issue. Thank you for reporting this!
This week's top contributor is @rafaelfranca! Please join me in thanking Rafael and all these awesome people who dedicated their time to help improve Rails! <3 <3 <3
This is a continuation of this commit. Naming a scope public, private and protected will generate a class method with the same name, which conflicts with the built-in methods with the same name which controls method visibility.
This issue of our newsletter won't be complete without a mention of @tgxworld's awesome work! In fact he submitted more pull-requests than we have room for, so you should just follow him on Github!
Watch a few core team members help touch search its soul while fixing a bug caused by this previous change in the method.
Wrapping Up
And that's it for this issue of This week in Rails, I hope you enjoyed it! 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!
