Releases: ngx-translate/core
Releases · ngx-translate/core
v7.2.1
v7.2.0
v7.1.0
v7.0.0
7.0.0 (2017-06-07)
Bug Fixes
Features
- TranslateService: new
stream
method to get an observable of translations that updates on lang change (d84c69b7, closes #330)
Breaking Changes
- shouldMerge option of the
setTranslation
method was only doing shallow merging using Object.assign. It is now doing deep merging of objects and arrays, which is what was initially intended (hence the name).
v6.0.1
v6.0.0
v6.0.0-beta.1
This release has a lot of breaking changes, read the migration guide to help you with the transition.
6.0.0-beta.1 (2017-02-03)
Features
- rename: the library has been renamed ngx-translate following the new official naming convention (you should not use the version number for angular libraries, unless it is specifically for one version). This repository is now named "core" and available on npm under the name
@ngx-translate/core
. - module: modularize everything, the parameter for the method
forRoot
has changed and is now an object that you can use to specify a loader, parser and missing translations handler (instead of just the loader) (de2d56c) - TranslateLoader: removed static loader from core, it is now named
HttpLoader
and has its own repository (0c0b82f) - TranslateModule: adding forChild method to use in lazy loaded modules (ac7b201)
- TranslateStore: added a store to share translations between instances of the service (b626c0e)
v5.0.0
<a name"5.0.0">
5.0.0 (2016-12-20)
Bug Fixes
- TranslateService:
- Translate Directive:
- the directive listens to
onTranslationChange
events now (20881950)
- the directive listens to
Features
- Added default fallback language to English (15a75c24)
- TranslationService: getting translations for default lang when it's set (20881950, closes #332, #336)
Breaking Changes
- we will now fetch the translations for the default lang when it is set (if they are not already available). Also the default lang is now automatically set to the first lang that receives translations (if it is still undefined at that time). Setting the default lang will override this default behavior, so this will probably not break anything for you, but if you set the translations for the default lang first then you don't even have to call
setDefaultLang
anymore. (20881950)
v4.2.0
v4.1.0
<a name"4.1.0">
4.1.0 (2016-12-05)
Features
Usage:
<div [translate]="'HELLO'" [translateparams]="{param: 'world'}"></div>
Or even simpler using the content of your element as a key:
<div translate [translateparams]="{param: 'world'}">HELLO</div>