fix: Properly render i18n translations client-side#139
Merged
baptistegrimaud merged 2 commits intomainfrom Feb 6, 2026
Merged
Conversation
GauBen
approved these changes
Feb 5, 2026
baptistegrimaud
force-pushed
the
fix-i18n-client-side
branch
from
08c8947 to
bf55915
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes Jahia/javascript-modules#317.
Description
Following the change in Jahia/javascript-modules#629, use
useTranslation()hook to correctly render i18n translations client-side.Tip
Documentation to guide the reviews: How to do a code review