TranslationManager

​

Initialization

setLocalesPath("/path/to/locales/{{lng}}.json");

import { setLocalesPath } from "msm-components/dist/services.js";

setLocalesPath("/admin/assets/locales/{{lng}}.json");

​

Exports

• setLocalesPath(loadPath)
• translate(...args)
• translations (a proxy for lazy translation access)
• tr(key, repository?) (loads/returns a single translation)
• loadTranslation(key, repository?)
• loadManyTranslations(...keys)
• loadByLangCodeForEntity(entityId, lang, repository?)
• loadByLangCode(key, lang)
• loadTranslationById(id)
• clearTranslationsCache()
• getLanguages()
• getAlphabetForActiveLanguage()

​

Examples

import { setLocalesPath, translate } from "msm-components/dist/services.js";

setLocalesPath("/assets/locales/{{lng}}.json");
const title = await translate("DashboardTitle");
const greeting = await translate("Greeting", { name: "Alex" });

import { loadManyTranslations } from "msm-components/dist/services.js";

const texts = await loadManyTranslations(
  "UserConfirmationDialogTitle",
  "UserConfirmationButtonOk",
  "AbortButton"
);

import { tr, translations } from "msm-components/dist/services.js";

const label = await tr("SaveButton");
const cancelLabel = await translations.CancelButton;

​

Notes

• If setLocalesPath() was not called, translation functions throw an error to make the misconfiguration obvious.
• The helper uses the unified service call mechanism under the hood (service/repository calls), so it relies on the built-in client instance provided by msm-components.
• Use clearTranslationsCache() when the active locale data has changed.