Best Practices for Managing Localization Dictionaries in Teams Splitting into Packs

This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.

Message originally sent by slack user U722X9GVQWA

What approaches have teams taken for localization dictionaries when splitting up into packs? A single large dictionary in the root config/locales? Or does each pack have its own locales for its own code? It seems like locales per pack is preferred, but could get difficult to manage and to move around all those keys which could become fairly manual as well.

Message originally sent by slack user U71TN2WF04X

At least in my work, we moved everything that was related to the packs content. Localization files, asdets used only there, we are even considering moving migrations (or at least new ones)

Message originally sent by slack user U723FWO60D1

<@U722X9GVQWA> off topic, what do you call pack? is it https://github.com/Shopify/packwerk ?

Message originally sent by slack user U722X9GVQWA

<@U71TN2WF04X> ty for your data point. <@U723FWO60D1> i’m mainly referencing a https://github.com/rubyatscale/packs