You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently if ShortenedThrowableConverter.maxLength is set to any value (say 1000) then that includes the exception message as well as stack trace length.
In case someone adds a large/dynamic exception message then it is possible that the whole stack trace is lost.
Describe the solution you'd like
proposal is to include a setting ShortenedThrowableConverter.maxErrorMessageLength which can be used to limit the length of error message being included.
So with maxErrorMessageLength set as 100 and maxLength set as 1000 it can be guaranteed that 900 limit will be used for stack traces.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently if ShortenedThrowableConverter.maxLength is set to any value (say 1000) then that includes the exception message as well as stack trace length.
In case someone adds a large/dynamic exception message then it is possible that the whole stack trace is lost.
Describe the solution you'd like
proposal is to include a setting ShortenedThrowableConverter.maxErrorMessageLength which can be used to limit the length of error message being included.
So with maxErrorMessageLength set as 100 and maxLength set as 1000 it can be guaranteed that 900 limit will be used for stack traces.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: