-
Notifications
You must be signed in to change notification settings - Fork 15
refactor: rename condition_pattern to required_input_pattern and condition_not_pattern to forbidden_input_pattern #587
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-09-pgf-3hs.13_unify_flow_compilation_paths_via_flowshape
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 534994a
☁️ Nx Cloud last updated this comment at |
38446ea to
acd3e0e
Compare
919577f to
be73fb9
Compare
acd3e0e to
534994a
Compare

Rename Condition Pattern Fields for Better Clarity
This PR renames the database fields and function parameters related to step conditions to improve clarity and better reflect their purpose:
condition_patterntorequired_input_patternto clearly indicate that this pattern must be present in the inputcondition_not_patterntoforbidden_input_patternto clearly indicate that this pattern must not be present in the inputThese changes make the code more self-documenting and align with the semantic meaning of these fields. The renaming is consistent across:
All tests have been updated to use the new field names, and the functionality remains unchanged.