We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The default handling of Throwable is to print the full stack, which may be too large.
Throwable
Actually, I don't think prepareLog should append the throwable to the message so that the subclass can decide what to do with them.
prepareLog
But in order not to break the behavior, could you make prepareLog() or getStackTraceString() open and protecte? Then I can change the format.
prepareLog()
getStackTraceString()
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The default handling of
Throwable
is to print the full stack, which may be too large.Actually, I don't think
prepareLog
should append the throwable to the message so that the subclass can decide what to do with them.But in order not to break the behavior, could you make
prepareLog()
orgetStackTraceString()
open and protecte? Then I can change the format.The text was updated successfully, but these errors were encountered: