Engineering
Our engineering is underpinned by principles that celebrate both the integrity of code and the ambition to innovate. This manifesto champions excellence, advocates for the adoption of cutting-edge technologies, and fosters an environment of continuous intellectual growth.
i18n practices
Rails gives us localization features via the rails-i18n gem. While the Rails guide describes the technical details on how to use it, it doesn't prescribe any guidelines on how to name and sort your localization strings. Here's my take on how a project's I18n strings should be sorted out.
Quote your strings
While the YAML format is liberal and quotation marks aren't needed, the consistency is always welcome. It also makes it less ambiguous for non-developers who may edit the YAML file.
Don't add punctuation
Some strings end in :. Don't place them in the YAML file. This will allow for the strings to be reusable later on.
Group by controller and action
Place your page's strings under their respective controller and action names. This allows to you take advantage of Rails's shortcuts. Also, always name your primary title as title.
Group strings for partials
The same concept should apply for partials. You can also use the t('.login') shortcut inside partial views.
Avoid top-level strings
Don't place strings on the top level such as t('and'). Place them on a parent, even an arbitrary one. If you can't think of a parent name, use common.
Avoid over nesting
Prefer to nest with just one level. Overly-complicated nesting can seem very arbitrary and confusing.
Familiarize yourself with defaults
The default locale file is available under rails-i18n.
Time and date
Don't use .strftime Use i18n to format timestamps. Define your time formats in time.formats. Listed below are the default time formats available in Rails. l(Time.now, format: :short) en: time: formats: default: "%a, %d %b %Y %H:%M:%S %z" short: "%d %b %H:%M"
Same with dates The I18n.l method also supports dates. Also, when creating new formats, add comments on what they should look like to help your teammates along.
Forms
Use ActiveRecord errors
Use form labels There are also conventions on where f.label will look up labels.
Dive into our latest musings and discoveries. Our blog is a window to the trends shaping the future and reflections on our journey.
Exploring horizons, sharing insights.
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
Mashup Garage, a premier software development team, specialises in crafting exceptional products for startups and enterprises. With expertise in React, Elixir/Phoenix, and Ruby on Rails, we deliver solutions that meet your unique needs. Our mission is to bring value backed by decades of technical expertise and global co-founding experience.
What do you need help with?
Build a project
Build a team
Consult
Speak to someone
Expect a guaranteed response from us in 1-2 business days.
United Kingdom
London
Islington, London
+44 738 777 3405
Philippines
Manila
3F Topy IV Building, 3 Economia Road, Bagumbayan, Quezon City, 1110
+63 917 3084089