Repository navigation
Feature/exceptions+error handling - #37
Closed
LuisCartucho wants to merge 5 commits into
Closed
LuisCartucho wants to merge 5 commits into
LuisCartucho wants to merge 5 commits into
Conversation
…' into feature/Exceptions+errorHandling # Conflicts: # server/api/Services/TransactionService.cs # server/api/Services/UserService.cs
This file contains hidden or 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
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.
Exception Handling Overview
This PR uses a centralized API exception system located in the Errors folder.
ApiException
Custom exception representing intentional API errors with an HTTP status code and message.
ApiErrors
Factory helpers (BadRequest, Unauthorized, NotFound, etc.) used in services to throw semantic, consistent API errors.
ApiExceptionMiddleware
Global middleware that catches exceptions, converts ApiException instances into proper HTTP responses, and returns 500 for unexpected errors.
Why:
Keeps controllers clean, avoids scattered try/catch blocks, ensures consistent error responses, and prevents leaking internal exceptions to clients.