-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Detailed exception messages are required. #38
Labels
Comments
Detailed exception messages thrown by TSTL have been updated like such below:
|
Have implemented until |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Until now, exceptions thrown by TSTL had not provided enough information.
Exception.message
had stored only fragmentary words. It may possible to inference reason of the exception occurrence by readingError.stack
, but it seems not intuitive:To provide detailed exception information in
Exception.message
level, I'll upgrade the TSTL to express the source object, method and parameters onto theException.message
property like such below:The text was updated successfully, but these errors were encountered: