-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Fix error serializer when using selectable output type #762
Comments
@timothycrosley, did you start working on this? I can create a failing test to start with unless you already did that. |
HTTP errors now don't crash when formatting the output, even if a `hug.output_format.accept()` formatter is used.
HTTP errors now don't crash when formatting the output, even if a `hug.output_format.accept()` formatter is used.
I have not started working on this yet, thanks so much for contributing the test case! I'll start working on fixing this tonight - against the giving test case - unless you would like to do so. Thanks! ~Timothy |
Hi @akaihola, Your fix has been pushed into PYPI release 2.4.8: https://github.com/timothycrosley/hug/releases/tag/2.4.8 Thanks! ~Timothy |
After the fix to #753 ("404 not found does not respect default output format"), the error serializer didn't work anymore if using a
hug.output_format.accept()
construct as the default output format.An example:
Looks like the
error_serializer()
function insideHTTPInterfaceAPI.server()
fails to provide therequest
andresponse
arguments toself.output_format()
.The text was updated successfully, but these errors were encountered: