From 2ae0aa6bfad766aeb8ee67b6335e50d3211ed869 Mon Sep 17 00:00:00 2001 From: Sebastian Szvetecz Date: Sun, 10 Sep 2023 22:27:28 +0200 Subject: [PATCH] Fixed typo in docs - projections.md customer -> custom --- website/src/docs/hotchocolate/v13/fetching-data/projections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/docs/hotchocolate/v13/fetching-data/projections.md b/website/src/docs/hotchocolate/v13/fetching-data/projections.md index 1df03cd294f..037b3275bae 100644 --- a/website/src/docs/hotchocolate/v13/fetching-data/projections.md +++ b/website/src/docs/hotchocolate/v13/fetching-data/projections.md @@ -45,7 +45,7 @@ services.AddGraphQLServer() Projections can be registered on a field. A middleware will apply the selected fields on the result. Support for `IQueryable` comes out of the box. The projection middleware will create a projection for the whole subtree of its field. Only fields that -are members of a type will be projected. Fields that define a customer resolver cannot be projected +are members of a type will be projected. Fields that define a custom resolver cannot be projected to the database. If the middleware encounters a field that specifies `UseProjection()` this field will be skipped.