-
Notifications
You must be signed in to change notification settings - Fork 5
status code cleanup #96
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
base: develop
Are you sure you want to change the base?
Conversation
Dragon1320
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whats here looks fine, but ik theres a lot of input validation in the search route that i do that probably throws 500s, just make that throw 400s instead if its a user input issue, but obviously keep it as 500 if its a genuine issue.
Dragon1320
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the input validation i referred to in the last review is specific to the search route, basically im throwing a lot of errors in the db service, this causes them all to be 500s as the controller doesnt know any better, so either move the validation that im doing in the service to the controller or find a way to distinguish between errors thrown in the service that should be 400s and 500s
fixes #79