mobrix-engine-plugin-localization v1.0.0

MoBrix-engine-plugin-localization

Improve MoBrix-engine system with a fully working localization system

Summary

• Getting started
  • Installation
  • Usage
• API
  • Actions
  • Selectors
• Integration with other plugins
• Included libraries
• Authors
• License

Getting started

Installation

Check MoBrix-engine guide to init the system

If you want to use this plugin with MoBrix-engine, install it:

npm i mobrix-engine-plugin-localization

Usage

Include this plugin inside your MoBrix-engine config file, and optionally set the localization field as an object, with the plugin settings:

const localizationPlugin = require("mobrix-engine-plugin-localization");

const config = {
  appName: "custom-app",
  plugins: [localizationPlugin],
  localization: {
    namespaces: ["custom", "common"],
    debug: false,
    fallbackLanguage: "en",
    supportedLanguages: ["en"],
    defaultNamespace: "",
    loadPath: "/custom-locales/{{lng}}/{{ns}}.json",
    titlesNamespace: null,
  },
};

module.exports = { config };

Create a json file, following the same path structure specified with loadPath parameter. For example, using this loadPath:

/locales/{{lng}}/{{ns}}

the localization instance will search for copies, starting from the public folder, inside locales folder, using actual language ({{lng}}) and used namespace ({{ns}}) to determine where to find the correct json file. So, you need a json file for each namespace, for each language. Check https://github.com/i18next/i18next-http-backend#backend-options for details. For completeness, this is a valid json, that need to be located inside <public_folder>/locales/en/custom.json:

{
  "custom_key": "Hey, this is a localized copy !"
}

Then you can retrieve it, with localization hooks, inside your components:

import { useTranslation } from "react-i18next";

export const CustomComponent = () => {
  const { t } = useTranslation("custom");

  return (
    <div>
      <span>{t("custom_key")}</span>
    </div>
  );
};

API

With the plugin itself, some other useful selectors and actions are exported by this lib, to easily work with any component

Config

This plugin adds a custom field inside the mobrix-engine config, localization. This new field contains some configuration options, used by i18-next:

• onLanguageChange : callbacks called everytime the language is changed
• namespaces : i18next preloaded namespaces
• supportedLanguages : i18next preloaded namespaces
• fallbackLanguage: default language, used when a copy is not available in a specific language
• loadPath: copies JSON files path
• defaultNamespace: default i18next namespace
• titlesNamespace: namespaces specifically used to determine page titles (to be used with router plugin)

Check the usage section for a real example

Actions

Import them from this lib:

import { changeLanguage } from "mobrix-engine-plugin-localization";

Then dispatch them from any part of your app:

import { changeLanguage } from "mobrix-engine-plugin-localization";

import { useDispatch, useSelector } from "react-redux";

import { Button } from "mobrix-ui";

export const LanguageButton = () => {
  const dispatch = useDispatch();

  return (
    <div>
      {["es", "it", "en", "de"].forEach((lang) => (
        <Button
          onClick={() => {
            dispatch(changeLanguage(lang));
          }}
        >
          {lang}
        </Button>
      ))}
    </div>
  );
};

Selectors

Import them from this lib:

import {
  getLocalizationConfig,
  getLanguage,
  getLanguages,
} from "mobrix-engine-plugin-localization";

Then use them from any part of your app:

import { getLanguage, getLanguages } from "mobrix-engine-plugin-localization";
import { useSelector } from "react-redux";

import { Button } from "mobrix-ui";

export const LocalizationDebugComponent = () => {
  const language = useSelector(getLanguage);
  const languages = useSelector(getLanguages);

  return (
    <div>
      <p>{`Actual language is ${language}`}</p>
      <p>{`Supported languages are ${languages}`}</p>
    </div>
  );
};

Integration with other plugins

• This plugin expose some fields to work with any other plugin. If you want to interact with it, using your custom plugin, you can add an interaction with localization plugin inside your custom plugin:

//Just a skeleton of a custom plugin that interacts with router plugin
const customPlugin = () => ({
  // Custom plugin stuffs

  interactions: [
    {
      plugin: "localization",
      effect: (localizationConfig) => {
        // Custom plugin stuffs

        //Add the custom callback
        localizationConfig.onLanguageChange.push(() => {
          alert("language changed");
        });
      },
    },
  ],
});

• Additionally, if you use mobrix-engine-plugin-url-checker too, you can change the language directly from URL, with query parameters, by passing the lang parameter with the language you want to set. Try it with MoBrix-engine playground - https://cianciarusocataldo.github.io/mobrix-engine?lang=en

Included libraries

• 118next - the localization system used under the hood
• MoBrix-engine-types - to use MoBrix-engine type definitions inside the plugin
• MoBrix-engine-tools - to use MoBrix-engine utils functions, to easily work with it
• MoBrix-utils - to use shared util functions during init process
• This library is written entirely with Typescript

Authors

• Cataldo Cianciaruso

License

This project is licensed under the MIT License - see the LICENSE file for details