fix(plugin-multi-tenant): relationTo arrays inflating filterOptions where query size#14944
Merged
JarrodMFlesch merged 6 commits intomainfrom Dec 16, 2025
Merged
fix(plugin-multi-tenant): relationTo arrays inflating filterOptions where query size#14944JarrodMFlesch merged 6 commits intomainfrom
JarrodMFlesch merged 6 commits intomainfrom
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
paulpopus
approved these changes
Dec 16, 2025
Contributor
|
🚀 This is included in version v3.69.0 |
zubricks
pushed a commit
that referenced
this pull request
Jan 6, 2026
…here query size (#14944) Before the plugin was looping over relationTo arrays and would build up duplicate tenant queries. Now it just ensures that there is at lease 1 tenant enabled collection and adds a single tenant constraint to the filterOptions. Helpful to note that the relationships are populated 1 at a time and the filterOptions receives `relationTo` arg, the injected filter checks to see if the requested relation is a tenant enabled collection also before applying the constraint.
teastudiopl
pushed a commit
to teastudiopl/payload
that referenced
this pull request
Jan 8, 2026
…here query size (payloadcms#14944) Before the plugin was looping over relationTo arrays and would build up duplicate tenant queries. Now it just ensures that there is at lease 1 tenant enabled collection and adds a single tenant constraint to the filterOptions. Helpful to note that the relationships are populated 1 at a time and the filterOptions receives `relationTo` arg, the injected filter checks to see if the requested relation is a tenant enabled collection also before applying the constraint.
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.
Before the plugin was looping over relationTo arrays and would build up duplicate tenant queries. Now it just ensures that there is at lease 1 tenant enabled collection and adds a single tenant constraint to the filterOptions.
Helpful to note that the relationships are populated 1 at a time and the filterOptions receives
relationToarg, the injected filter checks to see if the requested relation is a tenant enabled collection also before applying the constraint.