You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team is trying to figure out if it's safe to use the @fundamental-ngx/i18n to support multi-language and multi-locale in our Angular application. We actively use @fundamental-ngx/core and @fundamental-ngx/cdk in our project, so there is an idea to also use @fundamental-ngx/i18n to translate not only fundamental components but the entire application.
There is some public API available to use like fdTranslate pipe or TranslationResolver. As I see under the hood it's built on top of https://formatjs.github.io/docs/intl-messageformat/ library, so it fully supports ICU Message syntax. It also supports real-time translations, which is good. I did some experiments and it seems to me that the @fundamental-ngx/i18n might be a good fit for our needs.
So I have 2 questions just to be on the safe side:
Is it safe to build a translation mechanism on top of the @fundamental-ngx/i18n library? Is it stable enough and no breaking changes expected?
Can we use ICU Message syntax and assume that the @fundamental-ngx/i18n will continue supporting it in the future?
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
Our team is trying to figure out if it's safe to use the
@fundamental-ngx/i18n
to support multi-language and multi-locale in our Angular application. We actively use@fundamental-ngx/core
and@fundamental-ngx/cdk
in our project, so there is an idea to also use@fundamental-ngx/i18n
to translate not only fundamental components but the entire application.There is some public API available to use like
fdTranslate
pipe orTranslationResolver
. As I see under the hood it's built on top of https://formatjs.github.io/docs/intl-messageformat/ library, so it fully supports ICU Message syntax. It also supports real-time translations, which is good. I did some experiments and it seems to me that the@fundamental-ngx/i18n
might be a good fit for our needs.So I have 2 questions just to be on the safe side:
@fundamental-ngx/i18n
library? Is it stable enough and no breaking changes expected?@fundamental-ngx/i18n
will continue supporting it in the future?Thanks
The text was updated successfully, but these errors were encountered: