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
like this one have not gaven the root cause,
So I propose how about we show both the nearest exception , the root cause and clasp other exceptions between them?
like:
nearest exception .... clasped ,click to expand .... root cause
The text was updated successfully, but these errors were encountered:
the root cause:playframework/play-json#100
Sorry, something went wrong.
https://github.com/playframework/playframework/blob/master/framework/src/play/src/main/scala/views/defaultpages/devError.scala.html
and the
def throwableToUsefulException(sourceMapper: Option[SourceMapper], isProd: Boolean, throwable: Throwable): UsefulException
play.api.http.HttpErrorHandlerExceptions#throwableToUsefulException
both need a little change,otherwise , useful is a little :)
Sounds like a good idea!
No branches or pull requests
like this one have not gaven the root cause,
So I propose how about we show both the nearest exception , the root cause and clasp other exceptions between them?
like:
The text was updated successfully, but these errors were encountered: