feat: creating error class #67
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Joel-leal
force-pushed
the
joel/class-error-handling
branch
from
ef4054e to
51046aa
Compare
|
@Joel-leal you got conflicting files here when compared to main Please solve it by doing the following: In this branch, run Finally, push force to your branch. Let me know if you need any help 🙏🏼 |
src/packages/DAO/elections.dao.ts
Outdated
| if (!parsedData.success) { | ||
| throw new BadRequestError(parsedData.error.name); | ||
| } | ||
| const electionExist = await findByNameOrStatus(parsedData.data); // Error duplicate data |
There was a problem hiding this comment.
Can you add to your PR samples on how the error messages are looking in case of a failed parse please?
Thank you!
There was a problem hiding this comment.
I didn't understand what you meant by this. I modified the error message so that the BadRequestError has its own message instead of just relying on the error message from Zod. Could you provide more context about what you're asking?
Joel-leal
force-pushed
the
joel/class-error-handling
branch
from
0ab3fe3 to
aa65be7
Compare
Description
Handling errors in the back-end is essential to ensure system stability, provide clear responses to users, prevent sensitive information leaks, and facilitate the identification and resolution of issues during development and maintenance.
Changes
(list of the changes been made)
Notes
(leave here a few notes that could be useful to the reviewers)
I created an Error component for error handling in the backend
I did some error handling implementations using the errors component. With the change in architecture I did not change the routes file but rather the elections.dao file
Board issue