Localization configurations and setup.

Owned by Yogendra Pandey (Unlicensed)
Last updated: May 29, 2020 by Shreya B (Unlicensed)

Motive:

Fetching locale data specific to module selected. While using locale keys make sure keys belong to respective modules. While pushing locale keys to locale db, module name should be appropriate.

Key points:

  • 'rainmaker-common' module is used across application(e.g. Side bar, Header, login, logout etc), so we are keeping locale keys belonging to common module every time.

  • ‘rainmaker-pt' module is used for Property Tax module. Maximum keys of Property Tax module are under ‘rainmaker-pgr’ module. It is difficult to separate PT keys from PGR. That’s why in PT, we are using both ‘rainmaker-pt' and 'rainmaker-pgr’ module together to display all the locale keys.

  • If the locale key is displaying instead of corresponding text in the UI, make sure the locale key is present under correct module.

  • If any new module is created (e.g. ‘abc') then create the corresponding locale module adding prefix 'rainmaker-’ to it.

  • Make sure module name is present in the Navigation URL.

  • WithAuthrization HOC is responsible for calling the locale API for respective module. It is identifying the module name from navigation URL. (e.g. '/wns/apply?')

  • Do not call localization api anywhere else inside the application except tenantID specific locales.

  • Add new module to getModuleName() function under ‘egov-ui-kit/utils/commons.js’ file.