-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add i18n support #90
Add i18n support #90
Conversation
🦋 Changeset detectedLatest commit: 1b5dd6d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -0,0 +1,20 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's easier to maintain flat translation file like
admin.actions.user.email.title
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This nested notation is the only one supported by next-intl
const t = (key: string, options?: { [key: string]: any }) => { | ||
let translation = translations[key]; | ||
|
||
if (options && translation) { | ||
Object.entries(options).forEach(([key, value]) => { | ||
translation = translation!.replace(`{{${key}}}`, value); | ||
}); | ||
} | ||
|
||
return translation ?? key; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test for this function ?
#68