TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How OneGraph onboards users who are new to GraphQL

118 pointsby dwwoelfelover 6 years ago

8 comments

abhisuri97over 6 years ago
I don't think necessarily GraphQL is hard to understand as a concept. It's just difficult to figure out how to use it in an actual app context. How do I handle more complicated things such as authentication and, more importantly, what are acceptable and secure ways to structure your queries for auth (and things like that). I can certainly hack around with `context`, I just don't know what is actually good or not.
评论 #18991617 未加载
评论 #18992739 未加载
评论 #18993337 未加载
mrspeakerover 6 years ago
This is really cool! I think that for the demo you should make the &quot;Explorer&quot; open by default - I bet most people won&#x27;t realize what to do otherwise and will be intimidated (and just leave).<p>If possible it would be good to add default values too (like the &quot;ticker&quot; in the stock data set)!
评论 #18992445 未加载
评论 #19001168 未加载
sbr464over 6 years ago
I’m a big fan of graphql and use it for all frontend work.<p>I ran into one issue recently from a server side client use case where I needed to quickly consume an entire endpoint. Since you need to define each field in your query, it was more time consuming to create the requests. I also see the issue if fields are added, you would miss that data without updating your query.<p>Typically these are benefits when doing frontend work, to limit data, but I did find it annoying when just needing to quickly dump data.<p>For my own servers moving forward, I’m going to be adding a _doc json field for users that need traditional rest endpoint functionality in a query.
评论 #18992768 未加载
评论 #18992342 未加载
AznHisokaover 6 years ago
Naive question: Is GraphQL meant to be used only by the frontend developers to consume backend data, etc? And not by the actual consumers of the API (ie customers, users)? If not, I don&#x27;t see why consumers would ever want to use GraphQL.<p>Figuring out the syntax&#x2F;language to do something as simple as retrieving the first X items requires more thought than calling a dead-simple REST endpoint.
评论 #18993828 未加载
评论 #18994451 未加载
评论 #18991621 未加载
评论 #18991433 未加载
评论 #18993520 未加载
评论 #18991610 未加载
jeremynevansover 6 years ago
I&#x27;ve been a OneGraph user for a while now and I have to say the Explorer feature is still one of my favourite things about it.<p>In my opinion, a well designed API <i>should</i> be as easy to explore as folders on a computer, and the GraphiQL Explorer makes this the case by default.
timwisover 6 years ago
For me the barriers have been implementing the server (especially with authorisation logic); consuming it as a client was the relatively easy part.
评论 #18992313 未加载
评论 #18995296 未加载
NicoJuicyover 6 years ago
I&#x27;ve used graphql ( by force) in the past.<p>I like odata a lot more, but it&#x27;s more initial work
silentguyover 6 years ago
Is there any way to download OneGraph GraphiQL explorer binary? Is it open source?
评论 #18994845 未加载