-
-
Notifications
You must be signed in to change notification settings - Fork 571
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
'translateparams' directive in the example usage is not working. #355
Comments
Hi, you're right it should be How is it not working as expected (once you've set the correct |
If you assign the language key to the I am not sure if I am doing anything wrong here. Can you please check? Thanks in advance |
The directive is quite new, so it's possible that it's still buggy in a few use cases that I didn't test correctly. |
I just upgraded from 4.0 to 4.2 and I am trying out the directive. I can confirm that, regardless if
But this doesn't:
In the second case, there is no error in the console, but no text is displayed in the div. |
Same problem here with:
Before noticing this bug I had opened a SO question: http://stackoverflow.com/questions/41295910/ng2-translate-directive-not-working-while-pipe-is/41296133#41296133 |
Hello same problem here, if you use this : |
Same problem here. Using:
The @boughioul workaround makes it work. |
Thanks @ocombe! :D |
Fixed in 6.0.1 |
'translateparams' directive in the statement '<div [translate]="'HELLO'" [translateparams]="{param: 'world'}">' is not working. It seems like P should be in uppercase for 'translateparams'?
Even though the case is corrected to uppercase, the 'translate' directive does not seem to be working as expected. No error listed on the console. However 'innerHTML' directive is working fine for me.
Can anyone help? Is this a bug or my mistake?
The text was updated successfully, but these errors were encountered: