From c3f635922dc80e2968996e95d6b8de97c764cb97 Mon Sep 17 00:00:00 2001 From: gameofby Date: Thu, 17 Apr 2025 17:30:35 +0800 Subject: [PATCH] Fix: incorrect path for the mutations page --- src/pages/learn/schema.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/learn/schema.mdx b/src/pages/learn/schema.mdx index f38920d22a..b9ad71b912 100644 --- a/src/pages/learn/schema.mdx +++ b/src/pages/learn/schema.mdx @@ -413,7 +413,7 @@ Most of the examples we've covered on this page demonstrate how Object, Scalar, So far, we've only talked about using scalar values (like Enums or String types) as an input type for a field argument. However, you can also pass complex objects as arguments using an [Input Object type](https://spec.graphql.org/draft/#sec-Input-Objects), which is the last kind of named types in GraphQL that we'll explore. -This is particularly valuable in the case of [mutations](/learn/queries/#mutations), where you might want to pass in a whole object to be created. In SDL, Input Object types look similar to regular Object types, but with the keyword `input` instead of `type`: +This is particularly valuable in the case of [mutations](/learn/mutations/), where you might want to pass in a whole object to be created. In SDL, Input Object types look similar to regular Object types, but with the keyword `input` instead of `type`: ```graphql input ReviewInput {