feat: allow any operator in segment top rule#7427
feat: allow any operator in segment top rule#7427Zaimwa9 wants to merge 6 commits intodeps/bump-flag-engine-versionfrom
Conversation
There was a problem hiding this comment.
Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.
Once credits are available, reopen this pull request to trigger a review.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Docker builds report
|
|
Important Testing in progress…⏳ UI Tests: Running 294 tests… |
Playwright Test Results (oss - depot-ubuntu-latest-16)Details
Failed testsfirefox › tests/segment-test.pw.ts › Segment test 4 - Create ANY rule type segment and verify match changes when rule is updated @oss Details
Failed testsfirefox › tests/segment-test.pw.ts › Segment test 1 - Create, update, and manage segments with multivariate flags @oss Details
Playwright Test Results (oss - depot-ubuntu-latest-16)Details
Failed testsfirefox › tests/segment-test.pw.ts › Segment test 4 - Create ANY rule type segment and verify match changes when rule is updated @oss Details
Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
Failed testsfirefox › tests/segment-test.pw.ts › Segment test 4 - Create ANY rule type segment and verify match changes when rule is updated @oss |
Visual Regression16 screenshots compared. See report for details. |
…flagsmith into feat/allow-any-operator-in-segment-top-rule
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
Contributes to #7400
Adds frontend support for top-level
ANYrule type in the segment editor, enabling segments like(env=Prod AND id=1) OR (env=QA AND id=2).InlinePillTogglecomponent (with small/medium/large sizes + Storybook story) for the ALL/ANY selectorsegment_any_rule_typefeature flagAnd/Or) update based on top-level typediff-utils.ts) handles ALL sub-rule types and dynamic connectorsHow did you test this code?
Manually:
segment_any_rule_typeflag, open a project, create a new segmentANY— verify labels become "Or", button becomes "Add OR Condition", "Add AND NOT" disappearsALL— sub-rules convert back to ANY