Fabio Sussetto

Can this caveat be added to the project readme? I was lucky to read this thread, I was going to use this in a production application before reading about this...

@naysayer example: ``` // controller $scope.allDonePromise = $q.all([promise1, promise2, ...]); // template ``` The spinner will be shown until all the promises will be resolved. Note the promises cab be...

Very surprised this hasn't been implemented yet. Don't get me wrong, Quill looks amazing, just surprised this wasn't considered a very basic requirement for 1.0 I appreciate the benefits of...

I confirm this fixed the same issue for me.

@sdalezman I'm wondering if ignoring ids would actually be a good idea or not myself. I totally understand the reasons to ignore them, but at the same time, why not...

With the latest version (0.7.5), you can do it by using the growlMessages service like this: ``` .run(function ($rootScope, growlMessages) { $rootScope.$on('$stateChangeSuccess', () => { growlMessages.destroyAllMessages(); }); }); ``` Note...

@janpapenbrock you're right, I copied from one of our projects where we use ng-annotate to automatically deal with the problem.

Just experienced the same problem with this snippet: ``` componentDidMount () { this.fetchEvent() } fetchEvent () { const eventId = parseInt(this.props.params.eventId, 10) eventActions.fetch(eventId) .then(() => { eventActions.setCurrentEvent(eventId) }) .done() }...