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

[Refactor] - Backend Error Handler #177

Open
2 tasks done
darmsDD opened this issue Jul 24, 2021 · 0 comments
Open
2 tasks done

[Refactor] - Backend Error Handler #177

darmsDD opened this issue Jul 24, 2021 · 0 comments
Assignees
Labels
Backend Tarefas Relacionadas ao Backend could Could error treatment refactoring

Comments

@darmsDD
Copy link

darmsDD commented Jul 24, 2021

Description:

There is on Express a Error Handler that prevents the "try / catch" use (reducing code duplication). Since our backend function have similar try / catch blocks, it's possible to use this error handler function instead. Links to documentation below:

Remembering that not all try / catch blocks are equal, for example, the functions which send notification don't stop the function flow on try / catch where it's called, like chooseHelper, even though one error occurs in notification dispatch this function doesn't stop and the helper has to be chosen.

Acceptance Criteria:

  • Remove all try / catch duplications.

Tasks:

  • Check which try / catch blocks are similar.
  • Verify if there is a damage in remove try / catch abstraction
@darmsDD darmsDD added Backend Tarefas Relacionadas ao Backend error treatment refactoring labels Jul 24, 2021
@devsalula devsalula added the could Could label Jul 26, 2021
@darmsDD darmsDD self-assigned this Jul 28, 2021
@juniopereirab juniopereirab changed the title Tratamento de Erros Backend [Refactor] - Backend Error Handler Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend Tarefas Relacionadas ao Backend could Could error treatment refactoring
Projects
None yet
Development

No branches or pull requests

4 participants