From 64bb9b093a9cd39bd79f83027c4dde7027b262d7 Mon Sep 17 00:00:00 2001 From: Simpy Parveen Date: Wed, 27 Sep 2023 12:05:55 -0400 Subject: [PATCH] Update plugins-event-reference.mdx (#7739) `requestWillStart` -> `requestDidStart` (the former is not a real hook) --- docs/source/integrations/plugins-event-reference.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/integrations/plugins-event-reference.mdx b/docs/source/integrations/plugins-event-reference.mdx index 4a25d197898..df505f78a88 100644 --- a/docs/source/integrations/plugins-event-reference.mdx +++ b/docs/source/integrations/plugins-event-reference.mdx @@ -558,7 +558,7 @@ const server = new ApolloServer({ The `unexpectedErrorProcessingRequest` event fires whenever an "unexpected" error is thrown during request execution. "Unexpected" errors don't include common client data errors such as validation, parsing, or GraphQL execution errors. Instead, an unexpected error indicates a _programming_ error, such as a plugin hook throwing unexpectedly or Apollo Server encountering a bug. No matter the cause, Apollo Server masks this type of error from a client. -Note this hook is on the top level of the plugin rather than on the object returned from `requestWillStart`, because this hook triggers if `requestWillStart` throws. +Note this hook is on the top level of the plugin rather than on the object returned from `requestDidStart`, because this hook triggers if `requestDidStart` throws. #### Example