-
Notifications
You must be signed in to change notification settings - Fork 142
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
Error handling #112
Comments
Good Point, I would like to start an unstable branch and implement promises, then we could handle errors with the promise api. want to help? or have or suggestions? |
Personally I would take the lazy way out and just throw that line inside of a try/catch(err), with a return of the error. I don't know much about the JS promise API, but at the moment the support looks very low: |
OK, I added error handling. See this Gist: https://gist.github.com/djvs/7c82f7395624d85c7e03 specifically lines 96 and 185-219 (one big try-catch). This adds support for an optional error-catcher attribute in the <form> tag. You may want to double check, I basically used your method for the ng-upload attribute. |
This would be huge for me. +1 |
I will try to incorporate it by the weekend, I have been so busy, if you Thanks Tom On Thu, Jul 31, 2014 at 1:49 PM, Ken Caron notifications@github.com wrote:
Tom Wilson This e-mail may contain information that is confidential, privileged or |
Added to master js, but not released... Let me know if you see any issues: |
How do we handle errors in the new uploadComplete style? Apparently it doesn't trigger at all when the server throws an error - instead ng-upload.min.js throws:
The text was updated successfully, but these errors were encountered: