-
-
Notifications
You must be signed in to change notification settings - Fork 588
Translation transformer handler #1554
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
base: master
Are you sure you want to change the base?
Translation transformer handler #1554
Conversation
…formatted TranslateDefaultParser - All methods in the default parser are now protected to allow overriding - added getInterpolationReplacement() to allow customization of the replacements (getting values from the parameter object and formatting) - Improved formatter now renders Objects as JSON instead of [object Object] - Arrays are rendered with ", " instead of just ","
…nslation text is found. Isolated function to receive translation text from the translations with fallback to default language.
… TranslateStore to use better encapsulation. From outside, these event handlers are now visible as Observables and not EventEmitters to prevent users from outside calling emit(). Internally now using Subjects instead of EventEmitters. ngx-translate#1513
Instead, the function now uses the currentLang and defaultLang internally to get the values from the store directly.
getValue() is protected and can be overwritten. Fixed some lint warnings.
Add urls to link the repo with the npm page
Added Urls to repo
refactor(esLint): prefix
We already have this functionality in form of the translate compiler. |
I considered using the compiler to flatten the tree structure, but the cost is that it has to process the entire file every time it is loaded. |
Introduce a hook or extension point that allows modification of the raw translation value before the interpolation phase begins.
Issue: #1555