fix(ui): monomorphic relationship fields don't support multi-select with in/not_in operators#15886
Merged
Merged
Conversation
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.
|
paulpopus
approved these changes
Mar 10, 2026
Contributor
|
🚀 This is included in version v3.79.1 |
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
Fixes relationship filter UI to support multi-select when using
inornot_inoperators, regardless of the field'shasManyproperty. Previously, onlyhasMany: truefields supported multi-select, making it impossible to filter by multiple values onhasMany: falserelationship fields.Key Changes
Changed multi-select logic from
hasManyonly tohasMany || ['in', 'not_in'].includes(operator)hasMany: falsecan now select multiple values within/not_inoperatorsUpdated test helpers to support array values in filter inputs
Added e2e tests for multi-value filtering on
hasMany: falserelationship fieldsDesign Decisions
The
inandnot_inoperators semantically expect arrays of values, so the UI should support multi-select regardless of whether the field itself stores multiple values. This aligns with how select fields already work - ahasMany: falseselect field still lets you pick multiple values when using "is in".Also clarified that polymorphic relationships (
relationTo: ['posts', 'users']) don't supportin/not_inoperators since they store{relationTo, value}objects and these operators only match on value.Fixes #15882