Look for language files in translations/moduleName folder
Description
Due to lokalize.co restrictions we should move the language files to new path in all UI modules: translations/moduleName. For example in case of ui-users the language files should move to translations/ui-users.
Therefore the stripes-translations-plugin must look for translations in both translations/ and translations/moduleName. Later when all UI modules moved their language to the new location the plugin doesn't need to search for language file in the root of translations folder.
All related documentations must be updated with the new language file path convention.
We already have fallback logic in place to source translations from the original package.json approach. Here is the check within gatherAllTranslations() that can easily be modified by testing for another directory:
Last I checked some modules were still making use of the package.json fallback, so we may want to retire that one rather than maintain three possible ways to source translations from a module.
Mike Taylor May 16, 2018 at 12:55 PM
I added as a watcher, since he created the WebPack plugin and will have the clearest sense of how this should best be done.
Due to lokalize.co restrictions we should move the language files to new path in all UI modules: translations/moduleName. For example in case of ui-users the language files should move to translations/ui-users.
Therefore the stripes-translations-plugin must look for translations in both translations/ and translations/moduleName.
Later when all UI modules moved their language to the new location the plugin doesn't need to search for language file in the root of translations folder.
All related documentations must be updated with the new language file path convention.