Apollo’s graphql-extensions package enables
requestDidStart to return an end hook that is called at the very end of the request lifecycle. It seems that with plugins, there is no explicit way to hook into this part of the lifecycle.
My assumption from reading the code is that this may be an intentional decision to remove redundancy between the request end hook and the
willSendResponse hook. Is that correct?
I’m migrating an extension that times the request from start to finish. There are a number of legacy errors in the request pipeline code that will not trigger
willSendResponse, so I wanted to double check.
When turning an extension into a plugin, should I replace my extension’s request end hook with a
willSendResponse hook? Or is there a more applicable lifecycle event in the works?