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

Handle serverside errors in Falcor better #452

Open
emilgoldsmith opened this issue Sep 14, 2018 · 0 comments
Open

Handle serverside errors in Falcor better #452

emilgoldsmith opened this issue Sep 14, 2018 · 0 comments

Comments

@emilgoldsmith
Copy link
Member

Expected Behavior

Serverside errors encountered in Falcor should be communicated better to the front-end. The front-end should be able to for example know what went wrong if relevant and maybe tell the user it was their mistake, or whether it's a bug

Current Behavior

Right now for example if the cache is corrupted so the front-end can't validate if an issue already exists correctly, it'll (even if strengthening our promise "catches" which they currently aren't) simply say it was a 500 error when it was a user error.

Possible Solution

Steps to Reproduce (for bugs)

  1. Throw an error in Falcor
  2. See ambiguous 500 error be transmitted, not the actual error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant