React API Reference
Components from @lingui/react
wrap the vanilla JS API from @lingui/core
. React components handle changes of active language or interpolated variables better than low-level API and also take care of re-rendering when locale or messages change.
Rendering of Translations
All i18n components render translation as text without a wrapping tag. This can be customized in two different ways:
- globally: using
defaultComponent
prop onI18nProvider
component - locally: using
render
prop orcomponent
on i18n components
Global Configuration
Default rendering component can be set using defaultComponent
prop in I18nProvider
. The main use case for this is rendering translations in <Text>
component in React Native.
Local Configuration
Prop name | Type | Description |
---|---|---|
className | string | Class name to be added to <span> element |
render | Function(props) -> Element | Component | Custom wrapper rendered as function |
component | Component, null | Custom wrapper component to render translation |
className
is used only for built-in components (when render is string).
Function(props)
props returns the translation, an id, and a message.
component
is rendered with the translation
passed in as its child:
import { Text } from "react-native";
<Trans component={Text}>Link to docs</Trans>;
// renders as <Text>Link to docs</Text>
To get more control over the rendering of translation, use instead the render
prop with a render callback. Function passed to render
will receive the translation value as a translation
parameter:
// custom component
<Trans render={({ translation }) => <Icon label={translation} />}>
Sign in
</Trans>;
// renders as <Icon label="Sign in" />
render
and component
also accept null
value to render string without a wrapping component. This can be used to override custom defaultComponent
config.
<Trans render={null}>Heading</Trans>;
// renders as "Heading"
<Trans component={null}>Heading</Trans>;
// renders as "Heading"
Lingui Context
Message catalogs and the active locale are passed via context in I18nProvider
. Use the useLingui
hook to access the Lingui context.
Lingui context object is exported from the package (import { LinguiContext } from '@lingui/react'
). It is not expected that you would need it, but it enables advanced scenarios if the behavior of I18nProvider
doesn't fit your needs.
I18nProvider
I18nProvider
provides Lingui context to all components in the subtree. It should be rendered as top-level component of your application.
I18nProvider
renders its children only after a locale is activated. This ensures that the components consuming i18n
have access to the translations.
Additionally, it subscribes to change events emitted by the i18n
object and re-renders all components consuming the Lingui context when messages are updated or when a new locale is activated.
Prop name | Type | Description |
---|---|---|
i18n | I18n | The i18n instance (usually the one imported from @lingui/core ) |
children | React.ReactNode | React Children node |
defaultComponent | React.ComponentType | A React component within which translation strings will be rendered (optional) |
defaultComponent
has the same meaning as component
in other i18n components. Rendering of translations
is explained at the beginning of this document.
import React from 'react';
import { I18nProvider } from '@lingui/react';
import { i18n } from '@lingui/core';
import { messages as messagesEn } from './locales/en/messages.js';
i18n.load({
en: messagesEn,
});
i18n.activate('en');
const DefaultI18n = ({ isTranslated, children }) => (
<span style={{ color: isTranslated ? undefined : 'red' }}>
{children}
</span>
)
const App = () => {
return (
<I18nProvider i18n={i18n} defaultComponent={DefaultI18n}>
// rest of the app
</I18nProvider>
);
}
useLingui
This hook allows access to the Lingui context. It returns an object with the same values that were passed to the I18nProvider
component.
Components that use useLingui
hook will re-render when locale and / or catalogs change, ensuring that the translations are always up-to-date.
import React from "react"
import { useLingui } from "@lingui/react"
const CurrentLocale = () => {
const { i18n } = useLingui()
return <span>Current locale: {i18n.locale}</span>
}
Components
The @lingui/react
package provides Trans
component to render translations. However, you're more likely to use macros instead because they are more convenient and easier to use.
This section is intended for reference purposes.
Trans
Prop name | Type | Description |
---|---|---|
id | string | Key, the message ID |
It's also possible to use Trans
component directly without macros. In that case, id
identifies the message being translated. values
and components
are arguments and components used for formatting translation:
<Trans id="my.message" message="Hello World"/>
<Trans
id="greeting"
message="Hello {name}"
values={{ name: 'Arthur' }}
/>
// number of tag corresponds to index in `components` prop
<Trans
id="link"
message="Read <link>Description</link> below."
components={{ link: <a href="/docs" /> }}
/>
Plurals
If you cannot use @lingui/macro for some reason, you can render plurals using the plain Trans component like this:
import React from 'react';
import { Trans } from '@lingui/react';
<Trans
id="my.plural.msg"
message="{count, plural, =1 {car} other {cars}}"
values={{ count: cars.length }}
/>