rails-i18n VS Cells

Note that if you are using rails-i18n, configuration is automatically available for many locales.

And this example of translation for Rails defaults: https://github.com/svenfuchs/rails-i18n/blob/master/rails/locale/en.yml

Also, download ja.yml from rails-i18n and place it in config/locales.

Everything else is set up like site/welcome, but here, we introduce pluralization for countable things. I18n is able to select the appropriate translation based on the variable passed to it. If you see that pluralization is not working well for your locale, it's a good idea to enhance your Rails app with the rails-i18n gem.

rails-i18n

No. That does not contain time only no date i cannot use that without also geting date output also: https://github.com/svenfuchs/rails-i18n/blob/62ffdacdf52e2895715c9d708118bd5ffc320f6a/rails/locale/es-ES.yml. See? This is why I pose question in this reddit.

The origin of this format start Ruby. The i18n-js format is a direct export of translations defined by Ruby on Rails. To export the translations, a Ruby gem can be used, that's completely disconnected from Rails and that can be used for the solely purpose of exporting the translations, even if your project is written in a different language. For JavaScript there's a companion JavaScript package. It comes bundled with all base translations made available by rails-i18n. Base translations allow formatting date, numbers, and sentence connectors, among other things.

The translations are accquired from rails-i18n project -- which is one of the first modules that does things like this.

The Rails Locale Data Repository seems to be the only comprehensive collection of formats but unfortunately I have not seen a single date/time format it uses that is an actual date time format used in the given locale.

The cherry on top was that Comfy gem depended on rails-i18n, which overwrote date I18n translations coming from russian gem, breaking translations on some of the pages. Surely enough, this resulted in another hour or so of debugging and fixing.

It can be used with Ruby on Rails or other frameworks because I implemented with trailblazer/cells.

I agree, though cells does still have a larger following.

Better official documentation for cells: https://trailblazer.to/2.1/docs/cells.html

So what about the world outside Rails defaults? There are quite a few independent projects trying to help build components in the Rails view layer, among the more famous being Draper (utilizing the decorators pattern) or Cells (full-featured components in views). In the end, we decided to take a deeper look into a relatively new one – the ViewComponent framework.

GitHub has recently posted an article about view_component: https://github.blog/2020-12-15-encapsulating-ruby-on-rails-views/ Before it gets too popular I think I should share my experience with cells So that developers can have another chance to re-think and pick what to use for "encapsulated view components".

This, combined with the fact that we are using cells gem for some view components, resulted in another couple of hours of hunting for the problem (it takes some time to debug what exactly and how exactly changed in Rails internals) and then fixing this problem. At this moment, I already spent over 8 hours debugging Rails internals, different gem internals, fixing application, fixing tests, screaming internally.