Port Q.allSettled to $q

[JGarrido]

The allSettled method would function very similarly to all, but would additionally prevent reject or resolve from returning until all requests are completed.

See Q's documentation for details:
https://github.com/kriskowal/q#combination

[IgorMinar]

I think we should just make is so that it's possible to monkey-patch $q and promise instances so that extensions like these could be built outside of the core and then just installed via bower.

that way you would just do bower install angular-q-allSettled or something of that sort and you'd have allSettled on $q. The same could be used to monkey-patch other helper functions as well as other helper functions.

the point is that we should keep the core small and use this kind of extension mechanism to add more stuff to the core.

@caitp is working on refactoring $q to use prototypical style so that we can add methods onto the promise prototype which will make them available to all instances.

adding allSettled is already possible via decorators so nothing prevents you from creating angular-q-allSettled extension package in bower.

[IgorMinar]

I'm inclined to mark this as won't fix because it doesn't belong to the core.

[JGarrido]

The thing is allSettled is arguably more useful than all, since rejections will cause all to prematurely return. Instead of a second function (which does seem a bit wasteful, I'll admit), I'd like to propose an optional second parameter (a boolean flag that defaults to false) which can be passed to all to instruct it to carry out all operations, regardless of a rejection on any specific one – a true and complete 'all'.

For example:
$q.all([promise1, promise2, promise3], true)

Also, for future reference, how does one determine what should and should not belong to the core?

[wizardwerdna]

@JGarrido I am thinking that it would require that much of the promises/A+ spec to create a working promises structure, adding the elements for notify/progress and a structure for creating, resolving and rejecting promises and assimilating foreign thenables. In short what is there already. Everything else can be built therefrom, and with the decorator facilities or Igor's plugin suggestion, can be integrated.

Next steps are to bring it to Promises/A+ 1.1, and reduce the footprint with the proposed prototypal refactoring.

This is consistent with Angular's minimalist approach -- not everybody (indeed most) do not require more than the basic promises structure plus $q.all, so it would be wasteful to ask everyone to pay the bytes to include more code ($q.all is a close question, but gives GREAT bang for the buck in particular in unwrapping contexts). But other functionality is required or convenient for some, so it would be important to permit them to add it as dependents when desired/required.

[insidewhy]

Implemented this and added it to the bower registry: https://github.com/ohjames/angular-promise-extras