S
In case it helps someone else, I have found a way to keep my translation files separate on the backend but combine them for use in i18n as @s-molinari describes in his article. I simply add new files and then combine them before export in the i18n/index.js file, like so:
import enUS from './en-us/index.json'
import es from './es/index.json'
import ar from './ar/index.json'
import enUSstrings from './en-us/strings.json'
import esstrings from './es/strings.json'
import arstrings from './ar/strings.json'
const enUSCombined = Object.assign({}, enUS, enUSstrings)
const esCombined = Object.assign({}, es, esstrings)
const arCombined = Object.assign({}, ar, arstrings)
export default {
'en-us': enUSCombined,
'es': esCombined,
'ar': arCombined
}
And voila! Now I can keep the actual translations modular while still using them in language switching anywhere in my app.
