fix: trashed documents still show as IDs in relationship responses#16102
Merged
Conversation
…led relationship population
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
…elationship population
r1tsuu
reviewed
Mar 30, 2026
r1tsuu
approved these changes
Mar 30, 2026
Contributor
|
🚀 This is included in version v3.81.0 |
milamer
pushed a commit
to milamer/payload
that referenced
this pull request
Apr 20, 2026
…ayloadcms#16102) # Overview When a relationship points to a collection with `trash: true`, soft-deleted documents were showing as raw IDs in responses instead of being omitted. ## Key Changes In the dataloader, trash-enabled collections now fetch with `trash: true` so soft-deleted documents are returned alongside live ones. `deletedAt` is merged into the select to ensure it's always present in the result. In `populate()`, the returned doc is checked for `deletedAt`. If set, the doc is trashed and `relationshipValue` is set to null. For hasMany, null entries are filtered from the array after all row promises settle. For single relationships, the field is set to null. This correctly distinguishes trashed documents from inaccessible ones — access-denied or permanently deleted documents still fall back to the raw ID, unchanged from existing behavior. `depth: 0` is also unaffected. Fixes payloadcms#16022 --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1213860470196517
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.
Overview
When a relationship points to a collection with
trash: true, soft-deleted documents were showing as raw IDs in responses instead of being omitted.Key Changes
In the dataloader, trash-enabled collections now fetch with
trash: trueso soft-deleted documents are returned alongside live ones.deletedAtis merged into the select to ensure it's always present in the result.In
populate(), the returned doc is checked fordeletedAt. If set, the doc is trashed andrelationshipValueis set to null. For hasMany, null entries are filtered from the array after all row promises settle. For single relationships, the field is set to null.This correctly distinguishes trashed documents from inaccessible ones — access-denied or permanently deleted documents still fall back to the raw ID, unchanged from existing behavior.
depth: 0is also unaffected.Fixes #16022