Allow registering dynamic translations #471
Open
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.
In some use cases, other i18n solutions manage translations. In these cases, it is desirable to resolve the translations dynamically.
For example, I use tolgee as a way to create and manage translations. It already deals with resolving the locale, and potentially pulling new translations from a remote server. As such, it is not feasible to know the translations at build or app start time, or even resolve them immediately without using a fallback.
This PR just adds a mechanism to provide a function to the
registerTranslation
function, which will be called when getting the translation.In my application, this looks like this: