Skip to content
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

feat: make trigger condition optional #871

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

ChibiBlasphem
Copy link
Contributor

@ChibiBlasphem ChibiBlasphem commented Feb 24, 2025

This PR makes scenario trigger condition optional by:

  • Setting the trigger_condition_ast_expression field to NULL when patching scenario iteration if the trigger is an undefined node
  • Skipping trigger execution while evaluating scenario if the trigger is nil
  • Getting rid of validation scenario error when trigger is nil

Frontend PR: checkmarble/marble-frontend#711

Copy link
Contributor

@Pascal-Delange Pascal-Delange left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ChibiBlasphem ChibiBlasphem merged commit 5d45d45 into main Feb 24, 2025
3 checks passed
@ChibiBlasphem ChibiBlasphem deleted the feat/make-iteration-trigger-optional branch February 24, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants