-
Notifications
You must be signed in to change notification settings - Fork 100
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
Consider upgrading to Angular 1.4 #38
Comments
in my case, no problem |
Yes, no problem here either. It's just that the dependency is capped at 1.3 and it forces users to add a resolution to avoid conflicting versions of angular. This is particularly bothersome in CI and deploy scripts. |
With $httpProvider useLegacyPromiseExtension set to false i get errors because notify uses .success-syntax with $http. Maybe something to refactor as well |
I am also looking forward to the update of dependency version. |
I am looking forward to the update of dependency version as well. |
Is there any reason why Angular
~1.4
wouldn't work? Right now, this is the only dependency on my current project that forces me to use"resolutions"
onbower.json
.The text was updated successfully, but these errors were encountered: