-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
better error logging #926
Comments
@MikeKovarik thanks for filing this. The error you got is |
Fix typescript warning by showing error first, stack trace second. closes aurelia/framework#926
I'm submitting a feature request
aurelia-script 1.3.1
Current behavior:
If you make a typo, or on this case I forgot to add
async
to a function, you get a long but useless stacktrace pointing to inside of aurelia but nowhere in the stack trace does it give me any clue of what view, class, file is at fault. I've had this issue for years, ever since Aurelia was still in beta and it's been my biggest problem with aurelia ever since. Because despite having.developmentLogging()
enabled I'm subjected to tearing my app down and uncommenting it line by line until I find the needle in the haystackExpected Behavior:
Some general information about origin of the error - the file, line, or a class/method
The text was updated successfully, but these errors were encountered: