{"action":"created","issue":{"url":"https://api.github.com/repos/graphql-go/graphql/issues/115","repository_url":"https://api.github.com/repos/graphql-go/graphql","labels_url":"https://api.github.com/repos/graphql-go/graphql/issues/115/labels{/name}","comments_url":"https://api.github.com/repos/graphql-go/graphql/issues/115/comments","events_url":"https://api.github.com/repos/graphql-go/graphql/issues/115/events","html_url":"https://github.com/graphql-go/graphql/issues/115","id":135962373,"number":115,"title":"Error Handling?","user":{"login":"pyros2097","id":1687946,"avatar_url":"https://avatars.githubusercontent.com/u/1687946?v=3","gravatar_id":"","url":"https://api.github.com/users/pyros2097","html_url":"https://github.com/pyros2097","followers_url":"https://api.github.com/users/pyros2097/followers","following_url":"https://api.github.com/users/pyros2097/following{/other_user}","gists_url":"https://api.github.com/users/pyros2097/gists{/gist_id}","starred_url":"https://api.github.com/users/pyros2097/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyros2097/subscriptions","organizations_url":"https://api.github.com/users/pyros2097/orgs","repos_url":"https://api.github.com/users/pyros2097/repos","events_url":"https://api.github.com/users/pyros2097/events{/privacy}","received_events_url":"https://api.github.com/users/pyros2097/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/graphql-go/graphql/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-02-24T05:33:08Z","updated_at":"2016-08-09T13:36:22Z","closed_at":null,"body":"Graphql go right now swallows all errors and returns them back to the user. Sometimes we get database errors like `SQL State: conflicting foreign key` and this error goes back to the user. This is related to https://github.com/graphql/graphql-js/issues/28.\r\n\r\n We should add some add some ErrorHandling logic to prevent some of these errors for going back and also returning them back to the application so that it can know what to do with it (like log, mail).\r\n\r\nThe graphql scala https://github.com/sangria-graphql/sangria version have done a really good way of handling it here http://sangria-graphql.org/learn/ Maybe we should try their approach?\r\n"},"comment":{"url":"https://api.github.com/repos/graphql-go/graphql/issues/comments/238554692","html_url":"https://github.com/graphql-go/graphql/issues/115#issuecomment-238554692","issue_url":"https://api.github.com/repos/graphql-go/graphql/issues/115","id":238554692,"user":{"login":"bbuck","id":1244900,"avatar_url":"https://avatars.githubusercontent.com/u/1244900?v=3","gravatar_id":"","url":"https://api.github.com/users/bbuck","html_url":"https://github.com/bbuck","followers_url":"https://api.github.com/users/bbuck/followers","following_url":"https://api.github.com/users/bbuck/following{/other_user}","gists_url":"https://api.github.com/users/bbuck/gists{/gist_id}","starred_url":"https://api.github.com/users/bbuck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bbuck/subscriptions","organizations_url":"https://api.github.com/users/bbuck/orgs","repos_url":"https://api.github.com/users/bbuck/repos","events_url":"https://api.github.com/users/bbuck/events{/privacy}","received_events_url":"https://api.github.com/users/bbuck/received_events","type":"User","site_admin":false},"created_at":"2016-08-09T13:36:21Z","updated_at":"2016-08-09T13:36:21Z","body":"Is this not already possible with the current state of the library? I'm not sure if this feature existed at the time this issue was posted but as it stands a resolve function now has a return type of `(interface{}, error)` letting you receive and process any errors you have.\r\n\r\nShould this issue be closed?"}}
{"actor":{"display_login":"bbuck"}}