Repository navigation
feat(wf nested condition): allow nested condition on gateway step - #2064
Open
arnaud-moncel wants to merge 1 commit into
Open
arnaud-moncel wants to merge 1 commit into
arnaud-moncel wants to merge 1 commit into
Conversation
|
Coverage Impact This PR will not change total coverage. Modified Files with Diff Coverage (2)
🛟 Help
|
arnaud-moncel
force-pushed
the
feat/wf-nested-condition
branch
from
November 6, 2026 10:16
2f61628 to
bf29fb2
Compare
This branch has not been deployed
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.

Definition of Done
Fixes PRD-1171
General
Security
Note
[!NOTE]
Add nested And/Or condition groups to workflow gateway condition steps
ConditionStepExecutorevaluates each option's conditions as a root group with recursive group evaluation, and condition traces now include nested group results (condition-step-executor.ts).ConditionTreeParserrejects empty nested condition groups while keeping an empty root group valid, and fixes null-handling in itsisLeaf/isBranchtype guards (condition-tree-parser.ts).FilterGenerator.computeMatchnow handles empty branches: an emptyOrmatches no records and an emptyAndimposes no restriction, instead of emitting empty MongoDB logical-operator arrays (filter.ts).conditionschanged from a flat leaf-only array to recursive nodes in server-types.ts; consumers of the server condition type and ofConditionResultmust handle the new recursive shape.Macroscope summarized bf29fb2.