(langKey: string, filePath: string) => voidAdd a I18n translation by json file
(langKey: string, resources: VendureTranslationResources | any) => voidAdd a I18n translation (key-value) resource
(languageCode: string, keyPath: string[]) => string | undefinedv3.8.0Returns the string stored at the given path within the configurableOperation namespace of
the catalog for languageCode, or undefined if there is no entry there.
The resource is read straight out of the store rather than via t(), for two reasons. The
values contain { argName } placeholders which the Admin UI interpolates with the live
argument values, so they must reach the client untouched by ICU formatting. And the keys may
contain dots — a plugin is free to use a code such as acme.shipping.handler — which
i18next would otherwise treat as path separators.
I18n resources used for translations
Architecture reviews, custom plugin work, migrations, ongoing support. Get a hand from the team that builds Vendure.