Skip to content

Standardize error handling #20

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

Open
bhavaanikakarla opened this issue May 1, 2020 · 1 comment
Open

Standardize error handling #20

bhavaanikakarla opened this issue May 1, 2020 · 1 comment
Assignees
Labels

Comments

@bhavaanikakarla
Copy link
Member

bhavaanikakarla commented May 1, 2020

  1. Create Error Logs so that all bugs can be tracked. Integrate something like (https://airbrake.io/) to track and log errors. Would be easy to manage production user errors.

  2. Use backend error codes and centralize the error messages by creating Error Types on front end that would have fields like - Code, Name and Description for different errors.

Use these error message types for all errors. For every new type of error, add an entry to the Error Type.

@tejasa97
Copy link
Member

tejasa97 commented May 1, 2020

Yes, had deferred on this because I understood that error handling would be required only if there was any data we were taking from the user, i.e : POST requests, etc.
But right now, we only have faulty API requests being made from the frontend like /state/null, /state/undefined, which is primarily because of bugs in the frontend. do you think we should log/standardize these too? @bhavaanikakarla @yogesh-hackx @manan2002

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants