-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
continueOnError
option for eachAsync()
#11601
Conversation
…gregationCursor `eachAsync()` Fix #6355
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't tested it but only reading the code I think there is a small bug in there.
The preview in EachAsyncMultiError is only generated in the constructor with the passed Array, but not when we add an Error to the errors Array of the EachAsyncMultiError. So I assume the EachAsyncMultiError will not have the correct Error Message.
I guess we could change the let aggregatedErrors = null
to const aggregatedErrors = continueOnError && []
and push Errors directly in there and in the last Moment when we want to pass the Error Object to the callback we construct the actual EachAsyncMultiError-Object.
lib/error/eachAsyncMultiError.js
Outdated
|
||
|
||
/** | ||
* The connection failed to reconnect and will never successfully reconnect to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the comment correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me, with only a couple of comments.
Fix #6355