From bd604c7622f9619634b09b40afb83264083ad36d Mon Sep 17 00:00:00 2001 From: Michael Staib Date: Wed, 10 Aug 2022 23:54:03 +0200 Subject: [PATCH] Fixed execution engine docs --- .../hotchocolate/execution-engine/index.md | 21 ++++++++++++------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/website/src/docs/hotchocolate/execution-engine/index.md b/website/src/docs/hotchocolate/execution-engine/index.md index 41d83661a8b..001ee39ccbc 100644 --- a/website/src/docs/hotchocolate/execution-engine/index.md +++ b/website/src/docs/hotchocolate/execution-engine/index.md @@ -4,20 +4,25 @@ title: Overview In this section we will learn about the Hot Chocolate execution engine. - - - - # Request Middleware The GraphQL execution is abstracted into a request pipeline composed of many request middleware. Each request middleware represents one part of executing a GraphQL request, like the parsing of the GraphQL request document or the semantical validation of the GraphQL request document. + + # Field middleware Field middleware allows us to create reusable logic that is run before or after a resolver. It also allows us to access or even modify the result produced by a resolver. [Learn more about field middleware](/docs/hotchocolate/execution-engine/field-middleware) + +# Resolver Compiler + +The resolver compiler will compile for each resolver an optimized resolver pipeline. The resolver compiler can be customized by providing parameter expression builder. + + +