-
Notifications
You must be signed in to change notification settings - Fork 379
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
Localization loading randomly breaks when using requirejs #509
Comments
Can you provide more information about your use case? Consider usin http://plnkr.co/ to create an example - to better explain your issue. |
I found the error! The localization files should require knockout.validaion not knockout. That's why requirejs sometimes initialize the localization before knockout.validation. Regards, |
Thanks Michael. Great to see the module ID you sugget is |
@viceice do you want to submit a PR for this? |
If you want, i can do this. |
Sure, go ahead. Thanks. |
Ok, give me some minutes. :-) |
Reopening this issue because some localization files were not refactored. |
Which files? |
Oh. I see it. eg: I missed the the globals. I will check this |
Thanks @viceice for your interest on this. It seems there's more to fix than some AMD loading - somehow I missed that localization messages are not exported for nodejs when I first worked on it. |
Ok, haven't used it with node. Maybe some tests are required. Anything i can do? |
No worrries, I already started on this - there's only the fix for nodejs left. But thanks. |
Ok, no problem. 👍 |
It is not currently possible to configure a general requirejs dependency rule that covers all current and future localizations, and since the localization only tells requirejs it depends on knockout, the loading randomly breaks.
The text was updated successfully, but these errors were encountered: