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

[Bug] Some errors are not parsed properly #275

Closed
kmcginnes opened this issue Mar 20, 2024 · 1 comment
Closed

[Bug] Some errors are not parsed properly #275

kmcginnes opened this issue Mar 20, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@kmcginnes
Copy link
Collaborator

Community Note

  • Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the bug
Some requests do not check whether the response is in the 200 range and will attempt to parse the body as JSON and will fail. This leads to errors that are misrepresented.

  • OS: macOS 14.4
  • Browser: Arc (Google Chromium)
  • Graph Explorer Version: 1.5.1
  • Graph Database & Version: Amazon Neptune

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Errors in console

Expected behavior
A clear and concise description of what you expected to happen.

@kmcginnes
Copy link
Collaborator Author

This is resolved by PR #283

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: ✅ Done
Development

No branches or pull requests

1 participant