feat: Implement Custom Exception Handling with Error Codes and Messages #11
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.
Summary:
Introduced a custom exception handling mechanism to improve error management and standardize API error responses across the application. This includes a
CustomExceptionclass to encapsulate error codes, messages, and HTTP statuses, along with an updatedGlobalExceptionHandlerto process these exceptions.Changes Made:
Added
CustomExceptionClass:Updated
GlobalExceptionHandler:CustomExceptionand returns structured error responses withtimestamp,errorCode,message, andstatus.Example Usage in Controller:
SampleControllerto demonstrate how to throw aCustomException.Why This Is Needed:
Testing:
errorCode,message, andstatus.Related Issues:
Labels:
featureenhancementexception-handling