News for hackers. Stuff that matters.
Re:The GraphQL stack: How everything fits together by cheald on Thursday November 09, 2017 @11:28AM (#15663700)
That's entirely up to you and how you choose to implement your fields' resolutions.
Re:The GraphQL stack: How everything fits together by k__ on Thursday November 09, 2017 @12:45PM (#15664282)
Are there any best practices?
Re:The GraphQL stack: How everything fits together by cheald on Thursday November 09, 2017 @01:18PM (#15664531)
I don't know if there are for GraphQL in particular. I have my GraphQL implementation as a part of a Ruby app. graphql-ruby has this handy error handling doc: https://github.com/rmosolgo/graphql-ruby/blob/master/guides/... and there's the graphql-errors gem which sort of does this in a generic manner, allowing individual fields to fail without the whole query failing: https://github.com/exAspArk/graphql-errors