I'm using setLanguage() in my unit tests to ensure my localisation is functioning.
Now that resources are loaded asynchronously, you must wait for setLanguage() to complete before continuing.
I've made it work using the 'localized' event, but I don't find that intuitive - I would expect 'localized' to fire after translation, not just loading a language.
If there were a callback parameter to setLanguage, it wouldn't be so ambiguous.
I'm using setLanguage() in my unit tests to ensure my localisation is functioning.
Now that resources are loaded asynchronously, you must wait for setLanguage() to complete before continuing.
I've made it work using the 'localized' event, but I don't find that intuitive - I would expect 'localized' to fire after translation, not just loading a language.
If there were a callback parameter to setLanguage, it wouldn't be so ambiguous.
Paul