Next release

[UrzaUrza]

Hello, i would like to know when the next release is planned ?
Because i'm currently facing an issue with setDefaultLang and the modifications in this commit (610e4f1) seems to be what i need to fix my issue. (setDefaultLang returning an observable instead of void)

(FI: My issue is that the default language is not set because the "pending" observable is not resolved when i call translateService.instant)

[wamasimba]

As I couldn't wait either, I made a release of the current state of this repo, as @wamasimba/ngx-translate-core, version 16.0.5
See https://www.npmjs.com/package/@wamasimba/ngx-translate-core

[rbalet]

Hey @UrzaUrza.

We've prepared an RC: https://www.npmjs.com/package/@ngx-translate/core/v/16.1.0-rc.0
Feel free to use it and give us feedback if it works or not for you : )

[rbalet]

@CodeAndWeb I found the following, but I'm wondering if this is due to it being the release candidate.

I imported it locally and it seems to be working just fine.
So you have my green light

[UrzaUrza]

Hello @rbalet,

This version is fixing my issue but:

• The package @ngx-translate/core@16.1.0-rc.0 deployed on npm has not been built correctly (I built it locally for testing), which is why you got errors on the import
• The field "translation" of the "TranslateService" has been removed (breaking change), so for replacement I decided to use the "getTranslations" method of the "TranslateStore" but the type "DeepReadonly" is not exposed (I redefined it locally for the test) and should be.

[rbalet]

@UrzaUrza

1. same happened to me
2. For this one I'm not sure of the reason behind the depreciation, and IMO the store shouldn't be accessed directly
3. I know @CodeAndWeb which have the right to publish to be a bit overwhelmed at the moment, you'll need to be patient

@CodeAndWeb what is your take on it? (For the depracation? And do you have an idea on the when we could deliver a new version ?