Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed the broken link to the input-dto problem #92

Merged
merged 1 commit into from
Dec 29, 2024
Merged

Fixed the broken link to the input-dto problem #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/object/view/dto-language.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading