-
-
Notifications
You must be signed in to change notification settings - Fork 597
Promise is never resolved in case of server-side error when invoking Parse.Object.saveAll #494
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
Comments
Also, remove two duplicate unit tests.
Also, remove two duplicate unit tests.
@nrchandan did you open a pull request for this? I'm facing the same issue |
Why don't you just throw an exception if there is not an error handler like Promise does? Parse-SDK-JS/src/ParsePromise.js Line 78 in d7242d3
Maybe something like this if (this._rejectedCallbacks.length === 0) {
throw Parse.Error (error);
} |
@toddheslin I'm sorry but I have moved between projects and am no longer using this library. If the workaround suggested by @alexander-alzate works for you, would you recommend closing this issue? |
We have a node process that works on multiple batches of Parse objects. Each batch is saved through Parse.Object.saveAll. However, as soon as a batch errors out, the node process stops immediately and none of the subsequent batches get processed. We found that an error handling component was missing.
Raising a PR shortly. It adds just two lines of code.
The text was updated successfully, but these errors were encountered: