-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add basic error handling framework and 404 handling #50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prevents conflicts with Golang's default errors package.
Done in order to satisfy the error interface.
* Modify model function signature to also return error * Handle error in controller
* Update users' read handler signature to return errors * Do not panic on controller error * Wrap controller with API error handler to show correct status code
ngruiyanrena
approved these changes
Jul 18, 2023
This was referenced Jul 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #49.
Only updated one controller as a minimal example. Remaining controllers will be updated in a future PR
Overview
There are 2 kinds of errors:
We use a custom error interface
ClientError
for our errors that have a custom status code. This allows us to create custom error messages, such as those inHandleDBError
.Screenshots
Previously, reading an invalid user gives the wrong status code and output:
Now, reading an invalid user will give the correct result: