GraphiQL: GraphQL’s Killer App?
medium.com
GraphiQL: GraphQL’s Killer App?
1–10 of 18 posts
Re: GraphiQL: GraphQL’s Killer App?
#2[deleted]
Re: GraphiQL: GraphQL’s Killer App?
#3I am not sure why editors think a mark up is a good experience. Recently I have seen several editors that have markup on one side, and a formatted/stylized output on the editor. The output only sometimes feeds back to the markup, and usually does not have full functionality. This ends up being slow most of the time, and clicking/dragging/expanding text is not a good experience. They only thing they provide is validation feedback. But you still have worry about closure, indentation, formatting, etc. I usually default to using a light text editor and a shell watching validation.
Is everyone so sick of Windows forms that we can only edit text now? No GUI?
Re: GraphiQL: GraphQL’s Killer App?
#4I am building a GraphQL service to act as a endpoint-to-rule-them-all and GraphiQL has helped me sell the concept very well. It is much easier to talk about how queries work when a developer can just jump right in and start playing with it without having to setup any tooling or whatnot.
Re: GraphiQL: GraphQL’s Killer App?
#5On a related note, http://editor.swagger.io & http://petstore.swagger.io provide a similar UI for exploring REST APIs which have an OpenAPI (formerly known as Swagger) specification.
Re: GraphiQL: GraphQL’s Killer App?
#6Things like postman (https://chrome.google.com/webstore/detail/postman/fhbjgbifli...) exist for normal REST APIs. But it's lack of use suggests to me this isn't something people need.
Re: GraphiQL: GraphQL’s Killer App?
#7On a related note, http://editor.swagger.io & http://petstore.swagger.io provide a similar UI for exploring REST APIs which have an OpenAPI (formerly known as Swagger) specification.
When did the rename happen?
Re: GraphiQL: GraphQL’s Killer App?
#8Things like postman ( https://chrome.google.com/webstore/detail/postman/fhbjgbifli... ) exist for normal REST APIs. But it's lack of use suggests to me this isn't something people need.
Interactively querying REST APIS is a massive pain, doing anything useful requires multiple dependent queries, postman doesn't really help with that.
Being able to query a graph interactively is actually useful, I've used graphiql to explore the data graph to figure out the query I need for the data requirements of a component before I start writing the actual component itself.
Re: GraphiQL: GraphQL’s Killer App?
#9Am I the only one who designs endpoints to spit back usage instructions if you call them without arguments? This goes a long way toward helping devs use those endpoints, in my experience - and they can use normal tools (in particular, the network pane of Chrome Dev tools). This is not to take away from GraphiQL, but it doesn't seem like that much more than you get with such a convention.
Re: GraphiQL: GraphQL’s Killer App?
#10Am I the only one who designs endpoints to spit back usage instructions if you call them without arguments? This goes a long way toward helping devs use those endpoints, in my experience - and they can use normal tools (in particular, the network pane of Chrome Dev tools). This is not to take away from GraphiQL, but it doesn't seem like that much more than you get with such a convention.
No you're not the only one. But I do fear we may be some sort of "silent minority". I always felt that having human and machine readable instructions was part of trying to achieve "proper" REST, the full HEOTAS or whatever the acronym is. I admire the principle and the outcomes it strives for, but very much dislike the "wankery" that goes on over the topic sometimes.