Yup, I gotcha. That's actually why I'm not translating the module descriptions at the moment - because they're being pulled from the actual NPM module description key.
Mike TaylorJuly 3, 2018 at 11:07 AM
I'm sure you guys already thought of this, but just for the record ...
In doing this, we need to be sure that our UI modules are still well-behaved NPM modules, with readable English text in all the fields that the NPM package-file specification expects readable text in.
So if we want to change any existing field to be multilingual, specified by translation key, then we need to put the multilingual version of the field down inside the stripes part of the package file, and leave the top-level version as it is.
The module metadata being defined in the
package.jsonfiles is currently just regular strings. We need a way toReference keys/strings in the translation files
Parse the module metadata onload
Translate the module metadata
Make that translated metadata available to all code that is currently using hardcoded strings like
stripes.displayName