We currently have a Schema Designer that's fairly intuitive for the most part, and by "most part" I mean developers. Incorporating this tool to graphically show how your data relates would help the less tech-savvy domain experts on Scaphold.io tremendously. Thanks for your awesome work with this and GraphQL APIs (https://github.com/APIs-guru/graphql-apis).
I'd love to help contribute in any way!
Are you accepting pull requests?
After that, we are happy to assist you with an integration. Feel free to contact us on GitHub or directly https://apis.guru/about/
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 example to support paging), but the elegance hasn't hit me yet.
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.
Check it out here: https://github.com/acdlite/recompose/blob/master/docs/API.md...
Yes you can use the apollo client (the code above does) but as you can see that doesn't help the query size.
For scaphold.io I think you guys have done great on a lot of things, but the docs are really failing to explain the required relay schema and concepts prominently.
For relay, I'm trying to reserve judgement. First impression is it seems like an inelegant and cumbersome design. I did read their design goals, it just seems there were better ways to achieve them. And why introduce graph theory terminology for concepts that not really new in the database world?
Anyway people should checkout scaphold.io, I think it has the best UX going for gql saas.
A direction that'd be interesting to explore is a guided query writer. Perhaps have a floating query input box and if you click on a type, it adds a query. Then you could edit the query and as you add/remove fields & connections, it highlights the equivalent areas of the visualization.
BTW. We also included it in our list of public GraphQL APIs: https://github.com/APIs-guru/graphql-apis
For the list of endpoints, we offer three public endpoints ourselves: Digitransit HSL - Transit routes, stops and realtime schedules from Helsinki Regional Transport Authority, Finland: https://api.digitransit.fi/routing/v1/routers/hsl/index/grap...
Digitransit Waltti - the regional public transport authorities in Finland: https://api.digitransit.fi/routing/v1/routers/waltti/index/g...
Digitransit Finland - includes long-distance route data from Finnish Transport Agency: https://api.digitransit.fi/routing/v1/routers/finland/index/...
It depends on how likely you are to be sued for using this.
On the one hand, it's clear that the intent is to MIT license the software.
On the other hand, the MIT license requires specifying the year of the copyright along with the copyright holder (in addition to the actual text itself). As of right now, it's not clear who the copyright holder even is.
IANAL, but I would suggest that if you are at the point where you wish to modify and distribute the code, you could politely ask the copyright license holder to add a proper license block.
Or you can submit a PR :)
Because it's developed by Facebook, and Facebook really does view all of their data as a graph.
But even though critique is important FB has a lot to be proud of with their leadership in open source. I know some people have qualms with the license but in general I think they've inspired other companies go more in this direction.