fix(plugin-multi-tenant): hasMany tenant fields double-wrap arrays in filterOptions#15709
Merged
PatrikKozak merged 1 commit intomainfrom Feb 23, 2026
Merged
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
JarrodMFlesch
requested changes
Feb 23, 2026
packages/plugin-multi-tenant/src/filters/filterDocumentsByTenants.ts
Outdated
Show resolved
Hide resolved
PatrikKozak
force-pushed
the
fix/plugin-multi-tenant-hasmany-array-wrapping
branch
from
3d1ec4a to
b4f1022
Compare
JarrodMFlesch
approved these changes
Feb 23, 2026
PatrikKozak
deleted the
fix/plugin-multi-tenant-hasmany-array-wrapping
branch
Contributor
|
🚀 This is included in version v3.78.0 |
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.
What
Fixes double-wrapped arrays in filterOptions queries when tenant field has
hasMany: trueWhy
When a collection uses
hasMany: trueon the tenant field, documents store tenant IDs as arrays (e.g.,tenant: [id1, id2]).The
filterDocumentsByTenantsfunction was always wrapping the tenant value in an array without checking configuration, causing{ tenant: { in: [[id1, id2]] } }instead of{ tenant: { in: [id1, id2] } }.This breaks relationship field filtering in the admin UI.
How
Added explicit
hasManyparameter threaded throughaddFilterOptionsToFields→addRelationshipFilter→filterDocumentsByTenants.When
hasManyis true anddocTenantIDis provided, the value is used directly (already an array). Otherwise, it's wrapped in an array.Fixes #15690