-
Notifications
You must be signed in to change notification settings - Fork 888
Debug tslint error #2704
Comments
Reverting/changing that behavior was also on my agenda, because I think it causes more trouble than it's actually worth. There are several options:
Thoughts? @nchen63 @adidahiya @andy-hanson |
👍 for printing the whole stack trace. It's pretty cryptic otherwise, since there's no indication that the message is being printed because of an exception. |
@andy-hanson printing the stack trace by default doesn't play well will the exception thrown in |
Bug Report
Currently if an error is thrown while applying tslint rule it's logged as warning and only error message is included in log. This complicates debugging such cases. For example see #2696 where tslint printing the following log line:
without any details like stacktrace.
I suggest to add
debug
orverbose
option that will enable output of stacktrace.If that's ok I can submit a PR.
I'm not alone http://stackoverflow.com/q/43577136/746347
The text was updated successfully, but these errors were encountered: