Skip to content
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

Open
nfantone opened this issue Aug 12, 2015 · 5 comments
Open

Consider upgrading to Angular 1.4 #38

nfantone opened this issue Aug 12, 2015 · 5 comments

Comments

@nfantone
Copy link

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" on bower.json.

@pruge
Copy link

pruge commented Aug 13, 2015

in my case, no problem
angular 1.4.3
angular-notify 2.5.0

@nfantone
Copy link
Author

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.

faceleg added a commit to faceleg/angular-notify that referenced this issue Aug 16, 2015
@GustavSt
Copy link

With $httpProvider useLegacyPromiseExtension set to false i get errors because notify uses .success-syntax with $http. Maybe something to refactor as well

@mailinger-mate
Copy link

I am also looking forward to the update of dependency version.

@Poltuu
Copy link

Poltuu commented Nov 24, 2015

I am looking forward to the update of dependency version as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants