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
CommAngular swalows the errors throwed by services called from commands #9
Comments
I have been thinking about add a debug mode to print this type of errors during development or maybe delegate errors to angular $exceptionHandler. Could you print here the content of the error object managed by commangular?? commangular manage error as promises do, maybe if no handlers are found in commangular to manage an error commangular should launch an exception. |
Hi, e.g.: the Javascript console prints only the following message: "Cannot read property 'subscribe' of undefined commangular.js:490" and the requested error object which actually contains stack is as below. Maybe you could expose stack to the console as well? Thank you. error: TypeError |
Ok, to move the responsability for printing the error to the $exceptionHandler should be enough. I will add it as soon as I can |
Hello,
whenever error occurs on the service code called by command, the error is caught in commangular and simple message gets printed in console without providing stackstrace of where the error actually occurred.
Could you please fix it?
Thank you in advance.
The text was updated successfully, but these errors were encountered: