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
As a new litestar user, I've just started looking at documentation to test my application.
With the default example, un-handled errors are simply turning up as 500 internal server error without much to use.
Simply setting app.debug = True inside the test module is enough to have a proper traceback.
app.debug = True
Would it be possible to add this line on the first examples? Maybe there is a better way?
Looking up a the source for AsyncTestClient I see that there is a raise_server_exceptions option (in my case it is set to True, the default)
AsyncTestClient
raise_server_exceptions
Note
While we are open for sponsoring on GitHub Sponsors and OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
As a new litestar user, I've just started looking at documentation to test my application.
With the default example, un-handled errors are simply turning up as 500 internal server error without much to use.
Simply setting
app.debug = True
inside the test module is enough to have a proper traceback.Would it be possible to add this line on the first examples? Maybe there is a better way?
Looking up a the source for
AsyncTestClient
I see that there is araise_server_exceptions
option (in my case it is set to True, the default)Note
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard
The text was updated successfully, but these errors were encountered: