From 1d44a02892be43733e0e2b90e21b9ea6e63e7013 Mon Sep 17 00:00:00 2001 From: Arthur Milchior Date: Sun, 2 Jan 2022 11:41:04 +0100 Subject: [PATCH] Adding link to "schema page" It was quite akward that the name of a page was not a link to the page --- src/content/learn/Learn-Queries.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/learn/Learn-Queries.md b/src/content/learn/Learn-Queries.md index 6d9992fd30..3b74bf1ae0 100644 --- a/src/content/learn/Learn-Queries.md +++ b/src/content/learn/Learn-Queries.md @@ -212,11 +212,11 @@ Now, in our client code, we can simply pass a different variable rather than nee The variable definitions are the part that looks like `($episode: Episode)` in the query above. It works just like the argument definitions for a function in a typed language. It lists all of the variables, prefixed by `$`, followed by their type, in this case `Episode`. -All declared variables must be either scalars, enums, or input object types. So if you want to pass a complex object into a field, you need to know what input type that matches on the server. Learn more about input object types on the Schema page. +All declared variables must be either scalars, enums, or input object types. So if you want to pass a complex object into a field, you need to know what input type that matches on the server. Learn more about input object types on the [Schema page](/learn/schema). Variable definitions can be optional or required. In the case above, since there isn't an `!` next to the `Episode` type, it's optional. But if the field you are passing the variable into requires a non-null argument, then the variable has to be required as well. -To learn more about the syntax for these variable definitions, it's useful to learn the GraphQL schema language. The schema language is explained in detail on the Schema page. +To learn more about the syntax for these variable definitions, it's useful to learn the GraphQL schema language. The schema language is explained in detail on the [Schema page](/learn/schema). ### Default variables @@ -284,7 +284,7 @@ mutation CreateReviewForEpisode($ep: Episode!, $review: ReviewInput!) { Note how `createReview` field returns the `stars` and `commentary` fields of the newly created review. This is especially useful when mutating existing data, for example, when incrementing a field, since we can mutate and query the new value of the field with one request. -You might also notice that, in this example, the `review` variable we passed in is not a scalar. It's an _input object type_, a special kind of object type that can be passed in as an argument. Learn more about input types on the Schema page. +You might also notice that, in this example, the `review` variable we passed in is not a scalar. It's an _input object type_, a special kind of object type that can be passed in as an argument. Learn more about input types on the [Schema page](/learn/schema). ### Multiple fields in mutations