-
Notifications
You must be signed in to change notification settings - Fork 15
feat: add ifNot condition pattern for negative condition checks #584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 01-06-fix_step_array_map_overloads_to_use_topts_intersection_pattern_for_skippability_detection
Are you sure you want to change the base?
Conversation
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
View your CI Pipeline Execution ↗ for commit 3f4ff52
☁️ Nx Cloud last updated this comment at |
06596b7 to
d2515c8
Compare
238c72d to
bb09b62
Compare
d2515c8 to
6eea9d1
Compare
6eea9d1 to
d3c1db7
Compare
d3c1db7 to
4354fcb
Compare
bb09b62 to
6be7361
Compare
4354fcb to
3f4ff52
Compare

Add ifNot Condition Pattern for Step Execution Control
This PR adds a new
ifNotcondition pattern to complement the existingifpattern for step execution control. This enables more flexible conditional execution of workflow steps.Key changes:
condition_not_patterncolumn to thepgflow.stepstablepgflow.add_step()function to accept the new parametercascade_resolve_conditions()to support both patterns with AND semanticsThe
ifNotpattern works as follows:if, both conditions must pass (AND semantics)ifon one step andifNoton anotherThis feature enables more expressive workflow definitions, such as:
The TypeScript DSL has been updated to support the new
ifNotoption with proper type checking.