Document dynamic zone __component in REST update section#3150
Merged
pwizla merged 2 commits intoMay 11, 2026
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
reviewed
May 11, 2026
pwizla
approved these changes
May 11, 2026
Collaborator
pwizla
left a comment
pwizla
left a comment
There was a problem hiding this comment.
Thanks, @singhvishalkr.
I also downgraded the admonition from note to info here.
pwizla
added
pr: chore
source: CMS
contribution
pwizla
added a commit
that referenced
this pull request
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #2327 and the thread from Boegie19 spell out that dynamic zone payloads need a __component key on each entry so Strapi can pick the component schema. That was missing from the REST reference, so people were sending full arrays copied from GET responses and getting confusing results.
I added a short note under the update section of the REST API reference that calls this out and points readers at the Content-Type Builder UID (with shared.media as an example shape only).
Closes #2327.
Made with Cursor