You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Basically, setting jQuery.prototype.controller is a really bad move. AngularJS does that when it detects the presence of jQuery (see here: https://github.com/angular/angular.js/blob/master/src/Angular.js#L1303). As far as I can tell, this is purely for convenience. Unfortunately, because this method isn't namespaced you run into serious issues when other js libs rely on $.controller doing something not angular related.
In our case, JavascriptMVC expects $.controller to exist for it's purposes. When angularJS subsequently loads, it causes JavascriptMVC code to break in a serious way.
Is there some way we could include a way that you can specify that AngularJS should continue to use jQLite even if jQuery is available? Or better yet, have those convenience functions be namespaced?
Thanks,
Anton
The text was updated successfully, but these errors were encountered:
Basically, setting jQuery.prototype.controller is a really bad move. AngularJS does that when it detects the presence of jQuery (see here: https://github.com/angular/angular.js/blob/master/src/Angular.js#L1303). As far as I can tell, this is purely for convenience. Unfortunately, because this method isn't namespaced you run into serious issues when other js libs rely on $.controller doing something not angular related.
In our case, JavascriptMVC expects $.controller to exist for it's purposes. When angularJS subsequently loads, it causes JavascriptMVC code to break in a serious way.
Is there some way we could include a way that you can specify that AngularJS should continue to use jQLite even if jQuery is available? Or better yet, have those convenience functions be namespaced?
Thanks,
Anton
The text was updated successfully, but these errors were encountered: