[ ] Delegate Error Message Storage and Display to Frontend
[ ] Refactor Existing Try/Catch Blocks that do not handle errors
[ ] Setup a DB Table for Error Storage
[ ] Create a schema of the API error codes on Swagger
Acceptance Criteria
A global custom error class is available and correctly formats errors. ✅
It should optionally take a standard error object or an object containing an error code, HTTP status, and an optional message in its constructor.
Every error are handled by the error catcher (API).
The frontend is now responsible for storing and displaying error messages to the end user.
Existing try/catch blocks on the API have been refactored to handle errors.
A new table in the database has been set up to store errors.
Error handling refactor
We need to refactor the way we handle errors on our API. The goal is to create a more robust and maintainable error handling system.
Tasks
Acceptance Criteria