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
I'd like to suggest changing displayText from string to BehaviorSubject<string> to support dynamic change of display text and @ngx-translate, the HTML markup will become like, e.g.
<span*ngIf="option.displayText | async as menuText">{{ menuText | translate }}</span>
The text was updated successfully, but these errors were encountered:
I agree, @ngx-translate support must be added to the component, but using the translate pipe in the view will force everyone to install it so it may not be the better way to add support for translations.
I'm thinking in creating a custom pipe, that could use the injector to check if the TranslateService is available, an if it is available, then use it to get the translation. What do you think @hkvstore ?
I'd like to suggest changing displayText from string to BehaviorSubject<string> to support dynamic change of display text and @ngx-translate, the HTML markup will become like, e.g.
The text was updated successfully, but these errors were encountered: