Closed pgaertig closed 10 years ago
That may help someone: pin angular-growl-v2
to 0f71446dd3632234bdc0b9f050dcb20e86213179
in your bower.json
to have this awesome lib working back with 1.2.x.
Oh whoa - I could've sworn I tested this in 1.2.x and it worked fine. Anyway @JanStevens - how do you want to handle this? Should we create an Angular 1.3 branch and leave master compatible with 1.2? Or the other way around and have a 1.2 branch?
@vik-singh you did the good job. I investigated the issue and indeed 1.2.x deprecates old notation. Your change should work with 1.2.x. The trap is in demo.html
and README
which present the old way of registering the interceptor via responseInterceptor
. It is hard to notice by anybody what is the problem.
I have got an issue with angular-growl-2 master and my app which fatally breaks all http stuff in Angular 1.2.16 up to .21. Fortunately it also happens with demo/demo.html page. The growl doesn't work and after opening the page the browser console logs the following:
The problem is caused by c5b5a89647f683f9ace0fa67739e5d3ba445c637 introduced by #20 fix. Angular 1.3 API requires objects in interceptor mechanics however 1.2.x still needs a function. The template loading error is caused by malfunctioning interceptor.