-
Notifications
You must be signed in to change notification settings - Fork 1
Unify behavior for internal server errors #48
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
Milestone
Comments
php-coder
added a commit
that referenced
this issue
Mar 23, 2024
php-coder
added a commit
that referenced
this issue
Mar 26, 2024
php-coder
added a commit
that referenced
this issue
Mar 27, 2024
php-coder
added a commit
that referenced
this issue
Apr 22, 2024
php-coder
added a commit
that referenced
this issue
Apr 24, 2024
As we don't have a generic error handler, there is no reason to have a test for such behavior. Part of #48
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The generated apps should behave similarly in case of internal server errors. For instance, at the moment, express-based apps don't handle the exception and shutdown a whole application!
Let's return 500 status code in that case with
{ "error": "Internal Server Error" }
body.The text was updated successfully, but these errors were encountered: