Ahoy hoy! Tim (aka Godfrey) here bringing you all the latest from the Rails community. It’s been yet another killer week of activity as we continue to refine Rails 5 ahead of its upcoming launch 🚀. Don’t touch that dial - it’s gonna be a helluva show!
This week saw contributions from 26 fabulous people. 3 of those had a commit merged into Rails for the very first time. A big thank you to you all! ❤️
If you fancy seeing yourself up there next week, why not take a peek at the list of current issues? Improvements to the documentation can also be a great place to start!
Last week brought us an updated look at Rails by none other than DHH himself. The video offers a whirlwind tour of some of the most powerful features of the framework for newcomers in a tutorial that gets a blog set up in around 20 minutes. It also offers something for those looking to integrate newer features into their existing Ruby on Rails applications.
A recent regression caused #send_file to fail to halt the request cycle when used in a before_action. This is because the callback terminator checks for @_response_body , which is no longer set by #send_file. This fix updated to use #performed? instead.
If you use broadcasting to send messages to multiple loggers, you may have found that it does not silence all of them when told to do so. The fix updated to properly delegate #silence to all.
Kernel#caller_locations was introduced in MRI 2.0, and outperforms Kernel#caller in Module#delegate by around 10%. For the author this resulted in a faster boot time.
The new_framework_defaults file got a spruce this week, and documentation was updated to include better advice for upgrading to the new defaults from older apps.
The change also utilizes the update flag in several places to provide better messages catered for those only on the upgrade path.
That’s it from This Week in Rails! There were many other great contributions, too numerous to list here, but feel free to check them out!
Until next week!