Align Document Service note with connect payloads#3129
Merged
pwizla merged 3 commits intoMay 6, 2026
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
reviewed
May 6, 2026
pwizla
reviewed
May 6, 2026
pwizla
approved these changes
May 6, 2026
Collaborator
There was a problem hiding this comment.
LGTM, thank you!
I directly applied some fixes.
As a side note, I noticed a few trends in your PRs that should be fixed, so could you please add instructions to your AI model to:
- never use bold except for button names,
- never use prefixes in PR titles (per our git-rules.md)
Thank you!
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
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.
Closes #2904.
The relations doc claimed Document Service skipped relations even though the same page already shows
strapi.documents().update()withconnect, and the intro says REST relation payloads carry over. I folded that into one admonition: REST, GraphQL, and Document Service share the sameconnect/disconnect/setshapes, plus a short paragraph on the TS2353 typing gap the bot flagged so server-side authors know what to do until core types catch up.