Closed tobitos closed 9 years ago
I cannot remember why I cached the translation key in the first place. So I am going to merge your PR. Thanks.
Cool, thanks a lot. Would be great, if you could also update the version on npm. :)
I will release a new version as soon as I get home from work today.
I have released a new patch version just now. Sorry for the delay.
no worries, thank you for your work. :)
Currently, if the key of an already mounted translate-component gets changed in-between render calls, the translate component sticks to the old translation key, because "this.key" has already been set. This change allows for updating translation keys of already mounted translate components.
(This change is passing all the tests. Please tell me if you want me to write a new test for this.)