Skip to content

Clarify that private attributes are writable in GraphQL mutation inputs #3337

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

Draft
pwizla wants to merge 2 commits into
base: main
Choose a base branch
from
+4 −0
Draft

Clarify that private attributes are writable in GraphQL mutation inputs #3337

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
217a0c4
Clarify that private attributes are writable in GraphQL mutation inputs
github-actions[bot] Jul 16, 2026
de0b01d
Apply suggestion from @pwizla
pwizla Jul 16, 2026
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
4 changes: 4 additions & 0 deletions docusaurus/docs/cms/api/graphql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -491,6 +491,10 @@ For instance, for a "Restaurant" content-type, the following mutations are gener
| Update an existing "Restaurant" restaurant | `updateRestaurant` |
| Delete an existing "Restaurant" restaurant | `deleteRestaurant` |

:::note Private attributes in mutation inputs
Attributes marked `private: true` in a content-type schema are **included** in the generated mutation input types (e.g., `RestaurantInput!`) so they can be set via create and update mutations. Private attributes remain hidden from GraphQL query response types and filter inputs, as they are write-only from a GraphQL perspective.
:::

### Create a new document

When creating new documents, the `data` argument will have an associated input type that is specific to your content-type.
Expand Down
Loading