mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #1828] Better error messages for Graphql #579
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#579
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sawa-ko on GitHub (Sep 13, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1828
Originally assigned to: @H-thompson on GitHub.
Is your feature request related to a problem? Please describe.
Currently the application only says to press F12 to see the error, but the error is not readable.
hoppscotch
Graphql Playground
With the Graphql Playground error message you can easily know what is wrong, while with the hoppscotch error message you don't know what is wrong because the error is not readable.
Describe the solution you'd like
Display a more readable error message to understand what is going wrong.
Describe alternatives you've considered
None.
Additional context
No.
@H-thompson commented on GitHub (Sep 19, 2021):
I would like to take this feature on if it's not already being worked on. As part of the process of pulling through the error data I will ensure that it fits with the current localisation structure.
@liyasthomas commented on GitHub (Sep 19, 2021):
Hi @H-thompson thank you for showing the interest to work on this.
@StephaneBischoff commented on GitHub (Oct 3, 2021):
Hi @H-thompson @liyasthomas proposed a very simple fix. Let me know if you want some more improvements.
@sawa-ko commented on GitHub (Oct 4, 2021):
No, that's fine, thanks!