Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me.
Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
11–20 of 31 posts
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#12Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me. http://kevinsuttle.com/posts/dx-on-mobile-devices
The beauty of open source is that you can submit a pull request.
http://www.metabates.com/2011/05/24/stop-complaining-start-c...
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#13Glad to see our public transport schema as one of the demo options. However, it's not just Helsinki Region or Finland anymore: you can set up your own endpoints by loading OpenStreetMap and GTFS data into OpenTripPlanner. More info: https://digitransit.fi/en/developers
Thank you for making your GraphQL API publicly accessible.
Can you suggest a better name to be used in our demo?
BTW. We also included it in our list of public GraphQL APIs: https://github.com/APIs-guru/graphql-apis
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#14Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me. http://kevinsuttle.com/posts/dx-on-mobile-devices
Hey kevinSuttle.
Submit plz an issue with a screenshot specifying the size of the device you use.
We will try to fix it.
Or you can submit a PR :)
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#15Great project. I'm still deciding how much like gql itself. Trying scaffold.io and found the simplest code to get the first customer is const myQuery = gql` { viewer { allCustomers(first: 1) { edges { node { firstName } } } } } client.query({ query: myQuery }) .then((graphQLResult) => { console.log('success: ', graphQLResult.data.viewer.allCustomers.edges[0].node.firstName) }) All this verbosity has a reason (for exa…
viewer is a Relay convention for wrapping fields in an authenticated context. If the viewer does not resolve (not logged in) then data.viewer is null. It makes view permissions checking a lot easier and simpler.
Edges and node is also a Relay interface.
Graphql can be simpler if you don't use relay. Also the relay client is quite fat.
I use Apollo and I do use relay interface and conventions, just without the official Relay client. I like Apollo's simplicity a lot more.
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#16Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me. http://kevinsuttle.com/posts/dx-on-mobile-devices
Why do you act like this would be the most common thing in the world? It's certainly additional work and not really necessary for a HN launch, imo.
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#17Great project. I'm still deciding how much like gql itself. Trying scaffold.io and found the simplest code to get the first customer is const myQuery = gql` { viewer { allCustomers(first: 1) { edges { node { firstName } } } } } client.query({ query: myQuery }) .then((graphQLResult) => { console.log('success: ', graphQLResult.data.viewer.allCustomers.edges[0].node.firstName) }) All this verbosity has a reason (for exa…
viewer is a Relay convention for wrapping fields in an authenticated context. If the viewer does not resolve (not logged in) then data.viewer is null. It makes view permissions checking a lot easier and simpler. Edges and node is also a Relay interface. Graphql can be simpler if you don't use relay. Also the relay client is quite fat. I use Apollo and I do use relay interface and conventions, just without the officia…
Thanks, actually that is Apollo client, but the schema uses relay because that's what scaffold.io uses.
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#18Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me. http://kevinsuttle.com/posts/dx-on-mobile-devices
Why do you act like this would be the most common thing in the world? It's certainly additional work and not really necessary for a HN launch, imo.
Because the data I linked to?
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#19Disappointed to see this broken on small screens. Why it's assumed developers don't do work on mobile devices is beyond me. http://kevinsuttle.com/posts/dx-on-mobile-devices
Hey kevinSuttle. Submit plz an issue with a screenshot specifying the size of the device you use. We will try to fix it. Or you can submit a PR :)
iPhone 6S Plus.
Re: Show HN: GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
#20Great project. I'm still deciding how much like gql itself. Trying scaffold.io and found the simplest code to get the first customer is const myQuery = gql` { viewer { allCustomers(first: 1) { edges { node { firstName } } } } } client.query({ query: myQuery }) .then((graphQLResult) => { console.log('success: ', graphQLResult.data.viewer.allCustomers.edges[0].node.firstName) }) All this verbosity has a reason (for exa…
Hey there! This is Vince from Scaphold.io. Thanks for trying out our service. The query is as simple as it gets, but if you want to flatten the returned object, you can use recompose to flatten the returned properties.
Check it out here: https://github.com/acdlite/recompose/blob/master/docs/API.md...