Fixed the broken link to the input-dto problem

babyfish-ct · Dec 29, 2024 · 4ea976a · 4ea976a
1 parent 7f9a4c9
commit 4ea976a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/object/view/dto-language.mdx b/docs/object/view/dto-language.mdx
@@ -19,7 +19,7 @@ However, not all DTO types can be eliminated. Input DTO objects are hard to remo
 
 > For example, in GraphQL, although dynamic `GraphQLObject` data is returned for the client from the output perspective, static `GraphQLInput` data submitted by the client is accepted from the input perspective.
 >
-> Why does the GraphQL protocol define `GraphQLInput` as a static type? Because API explicitness and system security are very important requirements, please refer to [Problems with dynamic objects as input parameters](../../mutation/save-command/input-dto/problem).
+> Why does the GraphQL protocol define `GraphQLInput` as a static type? Because API explicitness and system security are very important requirements, please refer to [Problems with dynamic objects as input parameters](/docs/mutation/save-command/input-dto/problem).
 >
 > The problems faced by the GraphQL protocol are also faced by Jimmer, which must provide a complete solution.