[GH-ISSUE #468] Friendly minded GraphQL #178

New issue

Closed

opened 2026-03-16 13:53:51 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 13:53:51 +03:00

Owner

Originally created by @ac2epsilon on GitHub (Jan 2, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/468

Originally assigned to: @AndrewBastin on GitHub.

GraphQL can be friendly minded

It's hard for decent coder and impossible for novice to input right GraphQL query or mutator from the first take. And even from third. So: clicking on query have to fill request textarea with fully working template and click on type have to produce all-in-line repr like

query {
characters(page:${_page}) {
info {count...}
results {id name status species....}
}
} // note as we do ${_page} - yeah we make variables automatically and show them in the list below query window

All what user have to do is to remove fields she don't wish to see in result. And we will see how to instantiate response for further scripting...
AND also there are UX ideas of course related to naive list of GQL types and queries. It must be tree or something folding or such. As I asked in other issue and do it again I wish to use one of the toolkits namely Material or Vuetify or whatever and then we came back to UX.

Nobody does this. We are not competing. We dominate

Originally created by @ac2epsilon on GitHub (Jan 2, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/468 Originally assigned to: @AndrewBastin on GitHub. GraphQL can be friendly minded It's hard for decent coder and impossible for novice to input right GraphQL query or mutator from the first take. And even from third. So: clicking on query have to fill request textarea with fully working template and click on type have to produce all-in-line repr like query { characters(page:${_page}) { info {count...} results {id name status species....} } } // note as we do ${_page} - yeah we make variables automatically and show them in the list below query window All what user have to do is to remove fields she don't wish to see in result. And we will see how to instantiate response for further scripting... AND also there are UX ideas of course related to naive list of GQL types and queries. It must be tree or something folding or such. As I asked in other issue and do it again I wish to use one of the toolkits namely Material or Vuetify or whatever and then we came back to UX. Nobody does this. We are not competing. We dominate

kerem

2026-03-16 13:53:51 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 13:54:07 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 3, 2020):

GraphQL testing is very alpha and do need major polishing. Auto-suggestions on query section and Tree model etc are few of them. Let's track GQL UX improvements on this thread 👍

@AndrewBastin

@liyasthomas commented on GitHub (Jan 3, 2020): GraphQL testing is very _alpha_ and do need major polishing. Auto-suggestions on query section and Tree model etc are few of them. Let's track GQL UX improvements on this thread 👍 @AndrewBastin

kerem commented

2026-03-16 13:54:12 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 6, 2020):

@ac2epsilon thanks for opening this issue. Sorry, for the late response, I was away from Postwoman for the holidays.

Anyways, yeah you are right, the GraphQL UX needs a ton of polish and I will work on getting that properly done in the coming days.

@AndrewBastin commented on GitHub (Jan 6, 2020): @ac2epsilon thanks for opening this issue. Sorry, for the late response, I was away from Postwoman for the holidays. Anyways, yeah you are right, the GraphQL UX needs a ton of polish and I will work on getting that properly done in the coming days.

kerem commented

2026-03-16 13:54:17 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 8, 2020):

Since GraphQL section has improved tremendously over the past few week, I think this issue is stale now.

@liyasthomas commented on GitHub (Feb 8, 2020): Since GraphQL section has improved tremendously over the past few week, I think this issue is stale now.