-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The goal is to provide a platformized way to distinguish between errors at the Fusion layer. Today, errors are handled in one generic manner. Whether they are client type errors (ie validation, not found) or server type errors (ie authorization, server failures), these errors are logged the same and frontend applications classify them all the same without custom handling. Having these errors undistinguished creates a difficulty in filtering out specific error types that require different handling. This handling includes alerting on some error types but not others. For example: Co-authored-by: shYkiSto <siarhei@uber.com>
- Loading branch information
1 parent
f9bb3e1
commit 11f844f
Showing
2 changed files
with
24 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters