Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
cheald
on Nov 9, 2017
|
parent
|
context
|
favorite
| on:
The GraphQL stack: How everything fits together
That's entirely up to you and how you choose to implement your fields' resolutions.
k__
on Nov 9, 2017
[–]
Are there any best practices?
cheald
on Nov 9, 2017
|
parent
[–]
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
Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: