Skip to main content

I18n Improvements

Here are a list of i18n changes of Version 1.5:

Changed​

  • Key campaign.card.channel.link with translation value Link got the translation changed to Board Link
  • Key campaign.urls.sidebar-job-page-url with translation value Posting Job Page URL gpt the translation changed to Job Description URL

Added​

  • Key campaign.status-detail.status.in-progress with translation value In Progress
  • Key campaign.status-detail.status.online with translation value Online
  • Key campaign.status-detail.status.offline with translation value Offline
  • Key campaign.status-detail.status.not-processed with translation value Not Processed
  • Key common.load-more with translation value Load more...
  • Key common.working-time-indicator with translation value working
  • Key common.range.hours with translation value hours
  • Key common.range.days with translation value days
  • Key common.range.weeks with translation value weeks
  • Key common.range.months with translation value months
  • Key common.range.monthly with translation value monthly
  • Key common.range.yearly with translation value yearly
  • Key common.select-an-option with translation value Select an option
  • Key common.type-to-get-options with translation value Type to get options
  • Key common.there-are-no-options-for-search-value with translation value There are no options for {inputValue}
  • Key common.there-are-no-options with translation value There are no options
  • Key product.time-indicator-with-period-and-range with translation value {period} working {range}
  • Key product.details.channel.type.product_bundle with translation value Product Bundle
  • Key campaign.posting-details.description.allowed-html-tags with translation value Allowed HTML tags: {tags}
  • Key common.optional with translation value Optional
  • Key common.required with translation value Required

Empty list placeholder​

On our lists, when there are 0 items in the list, we display a generic message. For example when user has no campaigns, in the list of campaigns, we show We could not find any Campaigns. These were hardcoded and have been added to translations.

  • Key common.section-empty with translation value {prefix}{title}{suffix}

And the following have been added:

  • Key common.section-empty-prefix with translation value We could not find any
  • Key common.products with translation value Products
  • Key common.campaigns with translation value Campaigns
  • Key common.contracts with translation value Contracts

These get interpolated as: We could not find any Products with We could not find any being the prefix and the Products being the title.

Applied fixes​

HAPI Elements had some hardcoded strings, these are now translated:

  • The range and period indicator in Product Details in
    • Product Card visible on the Product Search
    • Inside the product details modal (and Product Details widget) when you click More Information button on the Product Card
      • next to the Calendar icon on top left
      • Processing Time
      • Time to Setup
      • Duration
  • The board type
    • In Product Card on the Product Search
    • Inside the product details modal (and Product Details widget)
    • In Basket
  • Form Select component used in multiple areas had its messages translated:
    • Type to get options
    • Select an option
    • There are no options for ${inputValue}
    • There are no options
  • Campaign status was being displayed as it was coming from Backend, it is now translated
    • In Progress
    • Online
    • Offline
    • Not Processed

New features​

Product Bundling​

There is a new feature called Product Bundling supported without any changes required apart from the new "Product Bundle" translation which is mentioned in the Added section.

Germany German and Netherlands Dutch translations added​

HAPI Backend supports in some areas mentioned in the What are the supported locales by HAPI Backend and what are they? section in Internalization

Ability to get Employment Types in locales supported by HAPI Backend​

We have added getEmploymentTypes function to Campaign module's Service submodule that returns the array of employment types in the locale supported by HAPI Backend.


This service function does not make a request to backend but rather returns an array of hardcoded employment types depending on locale set on Language module's State submodule. This is done to ensure backwards compatability in the future in case HAPI Backend adds an endpoint for FE to fetch these values.


Further more there may be a breaking chance explained in Changes to Submodules of Version 1.5

Utility submodule added to Language module​

Language module has had utilities submodule added which contains the following:

  • localeKeys object to use to set locales supported out-of-the-box by HAPI Elements
  • localesSupportedByBackend array that contains locales supported by HAPI Backend

Debug Panel Mock Buttons are now locale based​

We have a debug panel that we inject into your application on our sandbox environment. That debug panel has some utilities used during development and quality assurance.


In the Product tab inside Debug Panel, there is a Use Mock Filters button. That button now sets mock filters based on the locale that you set. It does however not work for locales not supported by HAPI Backend which are mentioned in Internalization, and it falls back to American English filters.


In the Campaign tab inside Debug Panel, there is a Use Mock Campaign Form button. That button now sets mock campaign values based on the locale that you set. It does however not work for locales not supported by HAPI Backend which are mentioned in Internalization, and it falls back to American English campaign values.