Closed Mordred closed 9 years ago
I have a fix but its not complete for release as I'm missing one part. In order to make this work we'd simply have to create an Aurelia Custom Attribute out of your used Translation-Attributes. Inside there, whenever the value changes or the thingy is initialized the first time, we can call the translation service automatically.
Now the only problem that I've left is to learn how to register an attribute with multiple names so that whatever the user provides can be used as the alias for the custom attribute.
Ok so at least for your current approach with naming the attribute t
the recent update should already solve your problem. Please report back if any other issues arise, will get the alias registration done in the meantime
Nice, it's working now for t
attribute. Thanks
Great, thx for the feedback
@Mordred the recent update now also introduces aliases
Nice .. very good job
If the
showInfo
becomestrue
, translations are not evaluated and theNot translated
text will be displayed.