Back away, bystander.
There’s a flame war going on, and we’d best contain it soon — the people need their Rails news!
Kasper pats flames and waters ferns in hopes we douse the mighty fires.
I’ll go brush up on campfire safety rules. Here, you read these.
A little while ago we crossed 4000 contributors – that’s crazy! Remember the old days when only one person contributed to Rails? Well, I wasn’t him so I don’t. Wups!
36 people made their mark this week. If you’re new, peruse the list and join us. If you do you’ll find a new friend waiting for you.
That friend is Rails bot. Fresh off the assembly line to bring those new to Rails a welcome message and tips. You’ll even get a reviewer assigned to help move things along. Come say hi with a pull request.
If you’re validating an email confirmation and you don’t care about the case, it can be skipped with
In Rails 5 if you’re using a migration method that isn’t reversible (meaning it can’t rollback) you will be warned about the offending method and how to roll your way out of that mess.
Banking on the
cache_key added to relations a while ago, any
cache calls in your views correctly use that instead of turning the relation into an array.
In Ruby’s OptionParser, if you wrap a parameter in brackets it’s considered optional.
By breaking it out of the brackets, writing
bin/rails test -e with an empty argument now raises a more appropriate error.
["innovative", "idea"].inquiry wouldn’t find anything because the symbol passed to any didn’t match any of the strings in the array.
Now everyone expects the string inquiry — and there’s room for “innovative” “ideas” once again.
That’s all for This week in Rails. As always, there are many more changes than we have room to cover here, but feel free to check them out yourself!
Have you been thinking about writing for us, but you’re scared of putting yourself out there? Don’t worry, you can help our editors improve their writing with thoughtful critique and general grammar policing.
You up for that? Tell Godfrey today.