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

Improve error handling in app #3271

Closed
frankeros opened this issue May 19, 2021 · 2 comments
Closed

Improve error handling in app #3271

frankeros opened this issue May 19, 2021 · 2 comments

Comments

@frankeros
Copy link
Contributor

frankeros commented May 19, 2021

Epic - Improve Error handling

Description
The app has a lot of unexpected behaviors due to a bad error handling strategy. Also, it’s really hard to identify a problem due to a lack of proper logging.

Propose
We need to improve the next topics:

Frontend:

  • Handle all JS errors from components and show them to the user softly.
  • Refactor all async returns (promises rejections and resolves) to a unique strategy.
  • All errors should be thrown through the logical/business layers adding some metadata (when is necessary) until the presentation layer, who is the one who decides how to react and/or show the error.
  • Improve a logging strategy with different log levels and UI representation.

Backend:

  • Refactor all async returns (promises rejections and resolves) to a unique strategy.
  • All errors should be thrown through the logical/business layers adding some metadata (when is necessary) until the API response layer, through an orchestrator to normalize all error responses.
  • Normalize the current use of the logger (easy error detection).
  • Improve the current logger to avoid spam logging.
@AlexRuiz7
Copy link
Member

@gdiazlo
Copy link
Member

gdiazlo commented Mar 16, 2023

Closing in favor of #4145

@gdiazlo gdiazlo closed this as not planned Won't fix, can't repro, duplicate, stale Mar 16, 2023
@wazuhci wazuhci moved this to Done in Release 4.5.0 Apr 21, 2023
@wazuhci wazuhci moved this to Done in Release 4.6.0 Jun 26, 2023
@wazuhci wazuhci removed this from Release 4.5.0 Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

No branches or pull requests

6 participants