+
+ {tokens.map((line, i) => (
+
+
+ {line.map((token, key) => (
+
+ ))}
+
+
+ ))}
+
+ )}
+ diff --git a/website/src/docs/greendonut/v10/api.md b/website/src/docs/greendonut/v10/api.md index 41aec213d60..acbceb892e9 100644 --- a/website/src/docs/greendonut/v10/api.md +++ b/website/src/docs/greendonut/v10/api.md @@ -1,5 +1,5 @@ --- -title: IDataLoader
diff --git a/website/src/docs/hotchocolate/api-reference/extending-filtering.md b/website/src/docs/hotchocolate/api-reference/extending-filtering.md index 7bb50b148ba..90c5a0c7835 100644 --- a/website/src/docs/hotchocolate/api-reference/extending-filtering.md +++ b/website/src/docs/hotchocolate/api-reference/extending-filtering.md @@ -19,34 +19,22 @@ Usually, it makes sense to divide the structure into two parts. The _field_ and The query below returns all movies where the franchise is equal to "Star Wars". The _field_ `franchise` where the filter is applied to and the _operation_ equals (`eq`) that should operate on this field. -``` +```graphql { - movies( - where: { - franchise: { - eq: "Star Wars" - } - }) { - name - } + movies(where: { franchise: { eq: "Star Wars" } }) { + name + } } ``` Fields can also form paths. In the query below there are two _fields_ `genre` and `totalMovieCount` and one operation equals `eq` -``` +```graphql { - movies( - where: { - genre: { - totalMovieCount: { - eq: 100 - } - } - }) { - name - } + movies(where: { genre: { totalMovieCount: { eq: 100 } } }) { + name + } } ``` @@ -296,8 +284,7 @@ A little simplified this is what happens during visitation: ```graphql { users( - where: # Create SCOPE 1 with parameter x of type User - # instance[0] = x + where: # instance[0] = x # Create SCOPE 1 with parameter x of type User # level[0] = [] { # Push property User.Company onto the scope diff --git a/website/src/docs/hotchocolate/api-reference/filtering.md b/website/src/docs/hotchocolate/api-reference/filtering.md index fecc4570d5b..8f84f3aaa8d 100644 --- a/website/src/docs/hotchocolate/api-reference/filtering.md +++ b/website/src/docs/hotchocolate/api-reference/filtering.md @@ -46,7 +46,7 @@ Getting started with filters is very easy, especially if you do not want to expl Hot Chocolate will infer the filters directly from your .Net Model and then use a Middleware to apply filters to `IQueryable
diff --git a/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md b/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md index 70fe926b3f2..8c490ef4f92 100644 --- a/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md +++ b/website/src/docs/hotchocolate/api-reference/migrate-from-10-to-11.md @@ -666,6 +666,7 @@ downstream schemas. ``` ## Batch responses + In v10, responses to batched operations were returned as a JsonArray. In v11 the default is to return MultiPartChunked responses. To switch back to JsonArray, configure the HttpResult serializer as follows: ```csharp diff --git a/website/src/docs/hotchocolate/api-reference/object-type.md b/website/src/docs/hotchocolate/api-reference/object-type.md index 1d79c57fa7b..693d51b6c2b 100644 --- a/website/src/docs/hotchocolate/api-reference/object-type.md +++ b/website/src/docs/hotchocolate/api-reference/object-type.md @@ -2,6 +2,8 @@ title: Object Type --- +import { ExampleTabs } from "../../../components/mdx/example-tabs" + The object type is the most important output type in GraphQL and represents the data we can fetch from our GraphQL server. The GraphQL SDL representation of an object looks like the following: ```sdl @@ -17,7 +19,8 @@ represent raw data that is passed into a field. > **Note:** Every single code example will be shown in three different approaches, annotation-based (previously known as pure code-first), code-first, and schema-first. However, they will always result in the same outcome on a GraphQL schema perspective and internally in Hot Chocolate. All three approaches have their pros and cons and can be combined when needed with each other. If you would like to learn more about the three approaches in Hot Chocolate, click on [Coding Approaches](/docs/hotchocolate/api-reference/coding-approaches). -**Annotation-based approach** +