How to implement provide context on global error handlers

[maimike]

I just check the below PR but still do not know how to implement. Any else can help me?
#1343

Thank you so much

[Whoaa512]

@theduyetmai, if you use the extensions API (which is not well documented, so I suggest reading the source). You can create a custom error tracking extension that will be passed the context to each of the lifecycle methods.

const { ApolloServer } = require('apollo-server')

import { GraphQLExtension } from 'graphql-extensions'

class MyErrorTrackingExtension extends GraphQLExtension {
    willSendResponse(o) {
        const { context, graphqlResponse } = o

        context.trackErrors(graphqlResponse.errors)

        return o
    }
    // Other lifecycle methods include
    // requestDidStart
    // parsingDidStart
    // validationDidStart
    // executionDidStart
    // willSendResponse
}

const server = new ApolloServer({
    typeDefs,
    resolvers,
    extensions: [() => new MyErrorTrackingExtension()],
    context({ req }) {
        return {
            req,
            trackErrors(errors) {
                // Track the errors
            },
        }
    },
})

server.listen().then(({ url }) => {
    console.log(`🚀  Server ready at ${url}`)
})

[maimike]

Thank you so much

[kosanna]

on which version of apollo-server it's supposed to work? I have 2.1.0, but still have context being undefined @Whoaa512

[Whoaa512]

@kosanna According to the release notes it should have gone out in v2.0.8

[omgrief]

Bumping this issue, the fix brought in to v2.0.8 does seem like it would be the fix to allow for the context to be accessible from within the formatError function, but it is not the case as it never gets passed to the actual formatter, and is just returned by the extension.