Rails I18n – Seven Best Practices That You Should Know About

Rails Internationalization (I18n) - Seven Best Practices That You Should Know About
Employ “Lazy” Lookups
One cool thing about I18n in Rails is that when naming and nesting your keys properly, you can
write less code inside the views and controllers. How is that possible? Well, let’s say you have a
view called ​about.html.erb stored inside the ​app/views/pages folder. Inside you wish to display
the page’s title:
1
However, this code can be as simple as:
1
In order for this to work, you need to nest the ​title​ key under the ​pages.about​scope:
1
2
3
pages:
about:
title: 'About us'
This works, because the scope is written properly: it contains the folder’s and the view’s name
(​pages​ and ​about​ respectively).
The same approach works for controllers, so having the following translation in place:
1
orders:
2
3
create:
success: 'Your order is created!'
You may create a flash message easily:
1
2
3
4
5
6
class OrdersController < ApplicationController
def create
# ...
flash[:success] = t(:success)
end
end
It’s really convenient, so don’t be lazy to employ the “lazy” lookups!
phraseapp.com | sales@phraseapp.com | +49-40-357-187-76 | twitter.com/phraseapp | facebook.com/phraseapp | linkedin.com/company/phraseapp