From 4f4a7c0a269883f98dfbdce72b76f8fc5f62ac2c Mon Sep 17 00:00:00 2001 From: Tejas Narsule Date: Tue, 28 Jul 2026 12:14:07 -0700 Subject: [PATCH] Fix formatting and improve clarity in schema.mdx The text for the example for `null` argument is in the wrong place. Notice it says `As we saw in the example above`, even though the example it is referring to is below. --- src/pages/learn/schema.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/pages/learn/schema.mdx b/src/pages/learn/schema.mdx index 6ad4d7e6d8..d82c76adfa 100644 --- a/src/pages/learn/schema.mdx +++ b/src/pages/learn/schema.mdx @@ -186,8 +186,6 @@ type Character { Here, we're using a `String` type and marking it as a Non-Null type by adding an exclamation mark (`!`) after the type name. This means that our server always expects to return a non-null value for this field, and if the resolver produces a null value, then that will trigger a GraphQL execution error, letting the client know that something has gone wrong. -As we saw in an example above, the Non-Null type modifier can also be used when defining arguments for a field, which will cause the GraphQL server to return a validation error if a null value is passed as that argument: - ```graphql # { "graphiql": true } { @@ -196,6 +194,7 @@ As we saw in an example above, the Non-Null type modifier can also be used when } } ``` +As we saw in an example above, the Non-Null type modifier can also be used when defining arguments for a field, which will cause the GraphQL server to return a validation error if a null value is passed as that argument: ### List