Skip to content
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

Chore: Email Feature Exception Handling to Global Exception Handling #596

Open
3 tasks
Am0du opened this issue Aug 22, 2024 · 0 comments
Open
3 tasks

Chore: Email Feature Exception Handling to Global Exception Handling #596

Am0du opened this issue Aug 22, 2024 · 0 comments
Assignees

Comments

@Am0du
Copy link
Contributor

Am0du commented Aug 22, 2024

Description:
Currently, the exception handling for the email feature is implemented in a specific class. To promote code reusability and maintainability, we need to refactor the exception handling logic for the email feature into a global exception handler.

Acceptance Criteria:=

  • Refactor existing email feature exceptions to be handled by the global exception handler.
  • Ensure the global exception handler returns a consistent ErrorResponseDto.
  • Update all relevant tests to reflect the changes.

Error Handling:
Ensure that all exceptions related to the email feature are caught by the global exception handler. The global exception handler should return a well-structured ErrorResponseDto with appropriate error messages, error types, and status codes.

Purpose:
This refactor will ensure that exceptions across the application are handled consistently, reducing duplication and improving code maintainability.

Expected Outcome:
Exceptions related to the email feature should be handled by the global exception handler, which should return a standardized error response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant