feat: add constraints for input patterns and improve cascade skip tests#611
feat: add constraints for input patterns and improve cascade skip tests#611jumski wants to merge 1 commit into02-14-fix_missing_skip_archivalfrom
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 8ef7352
☁️ Nx Cloud last updated this comment at |
565b7a8 to
a0602c5
Compare
pkgs/core/supabase/tests/add_step/condition_pattern_invalid_types.test.sql
Outdated
Show resolved
Hide resolved
pkgs/core/supabase/tests/add_step/condition_pattern_invalid_types.test.sql
Outdated
Show resolved
Hide resolved
a0602c5 to
4adfb3e
Compare
4adfb3e to
8ef7352
Compare
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-611.pgflow.pages.dev 📝 Details:
_Last updated: _ |

Add constraints and improve cascade skip functionality
This PR adds database constraints to ensure
required_input_patternandforbidden_input_patternare always JSON objects, preventing invalid pattern types. It also enhances the_cascade_force_skip_stepsfunction to:The changes include:
stepstable to validate pattern types_cascade_force_skip_stepsreturn the number of steps skipped_cascade_force_skip_stepsThese changes improve data integrity and make the cascade skip functionality more robust and predictable.