-
-
Notifications
You must be signed in to change notification settings - Fork 181
Common Translations update from Hosted Weblate #691
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| {} |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| {} |
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: oss-apps/split-pro
Length of output: 43526
🏁 Script executed:
Repository: oss-apps/split-pro
Length of output: 50374
🌐 Web query:
i18next returnEmptyString default fallback behavior official documentation💡 Result:
In i18next, the returnEmptyString configuration option controls whether an empty string is treated as a valid translation result [1][2]. The default value for returnEmptyString is true [1][3][2]. When set to true (default), i18next accepts an empty string ("") as a valid translation, and it will be returned as the translation value [1][2]. If you want to prevent empty strings from being returned and instead trigger a fallback (for example, to a fallback language or the key itself), you should set returnEmptyString to false [4][5][6]. When this option is false, i18next treats an empty string as if the key were missing, causing the translation process to continue searching through fallback options [4][5].
Citations:
🏁 Script executed:
Repository: oss-apps/split-pro
Length of output: 50375
🏁 Script executed:
Repository: oss-apps/split-pro
Length of output: 559
🌐 Web query:
next-i18next default configuration returnEmptyString i18next options💡 Result:
The returnEmptyString option is an i18next configuration setting that controls whether an empty string is treated as a valid translation result [1][2]. By default, it is set to true [1][2]. When set to false, i18next treats empty strings as missing translations, which triggers fallback mechanisms (such as falling back to a different language or returning the translation key) [3]. Because next-i18next is built on top of i18next, you can pass this option through to the underlying i18next instance. In your next-i18next configuration file (e.g., next-i18next.config.js), you should include it within the i18nextOptions object rather than at the root level of the configuration [4][5]. Placing it at the root level may cause warnings in some environments because next-i18next expects specific configuration keys [6]. Example usage: // next-i18next.config.js module.exports = { i18n: { defaultLocale: 'en', locales: ['en', 'de'], }, i18nextOptions: { returnEmptyString: false, // Set to false to treat empty strings as invalid }, //... other next-i18next specific options }; You can find comprehensive details on this and other i18next-specific settings in the official i18next configuration documentation [1].
Citations:
🏁 Script executed:
Repository: oss-apps/split-pro
Length of output: 1107
Omit the empty Hebrew translations. When Hebrew is enabled,
next-i18nextretains""by default and renders blank labels instead of fallback text. Hebrew is not currently listed innext-i18next.config.js.🤖 Prompt for AI Agents