Uncaught errors can not be easily logged

[chrisportela]

Either using django's logger or through some hook there needs to be a way that things like sentry can know about these uncaught exceptions.

Issue is primarily in graphql_django_view/__init__.py in dispatch() of GraphQLView

except HttpError as e:
            response = e.response
            response['Content-Type'] = 'application/json'
            response.content = self.json_encode(request, {
                'errors': [self.format_error(e)]
            })
            return response

[jhgg]

Working on this in graphql-core.

graphql-python/graphql-core#41

Planning to have that done by new years.

On Dec 23, 2015, at 8:30 AM, Chris Portela notifications@github.com wrote:

Either using django's logger or through some hook there needs to be a way that things like sentry can know about these uncaught exceptions.

Issue is primarily in graphql_django_view/init.py in dispatch() of GraphQLView

except HttpError as e:
response = e.response
response['Content-Type'] = 'application/json'
response.content = self.json_encode(request, {
'errors': [self.format_error(e)]
})
return response
—
Reply to this email directly or view it on GitHub.

[rattrayalex]

In graphql-python/graphql-core#41 (comment) @syrusakbary claims this was fixed. Should this issue be closed?