We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the frontend doesn't provide much useful debugging info when it fails to fetch the data it wanted from the API.
The frontend server will crash and log to the console. The logged message will just say "Retrieving games failed", with no further info.
But, you can see in the Django logs that it's dishing out HTTP 401/400 responses to the frontend.
We should ideally be able to tell from the logged frontend error, which of the following happened:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, the frontend doesn't provide much useful debugging info when it fails to fetch the data it wanted from the API.
How to reproduce
Actual behavior
The frontend server will crash and log to the console. The logged message will just say "Retrieving games failed", with no further info.
But, you can see in the Django logs that it's dishing out HTTP 401/400 responses to the frontend.
Expected behavior
We should ideally be able to tell from the logged frontend error, which of the following happened:
The text was updated successfully, but these errors were encountered: