Usage

Wraps your app to set the active locale and (optionally) merge additional translation catalogs + per-locale overrides. Astryx components inside the subtree resolve their strings against this context. If no provider is present, components fall back to the shipped English defaults.

import { InternationalizationProvider } from '@astryx-vue/core/InternationalizationProvider'

messages and overrides are both a map from a BCP 47 tag to a catalog keyed by the original @astryx.* message keys, so the same JSON shape works for a whole language and for a handful of keys. The two layers merge per key: a catalog replaces the shipped text for that locale, and the sparse overrides are laid on top. Overrides are keyed by locale, so a runtime locale swap picks up the right set.

dir only sets the direction Astryx reads. It does not touch the DOM dir attribute: set that on <html> or a wrapping element yourself, and pass the same value to both. getLocaleDirection(locale) derives the value from a tag.

Nesting works: the inner provider wins for its subtree.

Best practices

Guidance	Practices
Do	Give messages a whole-language catalog for your target locale, in the same shape as the Astryx locale JSON.
Do	Use a same-shape local catalog only when Astryx has not shipped that locale yet or you are testing in-progress translations.
Do	Use real BCP 47 tags such as fr-FR, pt-BR, or ar-SA; regional locales fall back to their base language before English.
Do	Set the dir attribute on <html> (or a wrapping element) yourself; the provider does not set it. Use getLocaleDirection(locale) to derive the value for both the provider and the DOM.
Don't	Cast custom catalog maps to any; ProviderMessagesByLocale and ProviderOverrides type a local catalog.

Examples

Common configurations, variations, and states.

InternationalizationProvider — Overrides

Billing region

Override a small number of Astryx strings without providing a full locale catalog.