You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this library to quickly replace calls that are currently Promise.all to avoid an issue with orphaned promises after one fails. However this throws an AggregateError on { failOnError: false } which changes the semantics.
It would be nice if it could keep the exception semantics, but still wait. I understand I can just replace things with allSettled or some such, although that also changes the semantics since the order of failure is lost.
The text was updated successfully, but these errors were encountered:
It won't leave promises pending with {stopOnError: true}. If promises are started, they will continue until they are done, but pAll won't await them or include their result. The proper way to handle this is with a signal. It should be pretty easy to include that here as it could just be passed down to p-map.
Hello,
I'm using this library to quickly replace calls that are currently
Promise.all
to avoid an issue with orphaned promises after one fails. However this throws anAggregateError
on{ failOnError: false }
which changes the semantics.It would be nice if it could keep the exception semantics, but still wait. I understand I can just replace things with
allSettled
or some such, although that also changes the semantics since the order of failure is lost.The text was updated successfully, but these errors were encountered: