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.

Sign up for GitHub

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

Jump to bottom

Make backend error more toast friendly #576

Open

MatoPlus opened this issue Aug 8, 2022 · 0 comments

Labels

Member

MatoPlus commented Aug 8, 2022 •

edited

Loading

Sherry made a suggestion to use prisma error codes => client string for error toast

Otherwise if no prisma code, return BE error msg directly

Should try to focus on common error toast, eg: branch/skills manager

action: gather list of possible error toats

MatoPlus added the nice to have label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment