Skip to content

Conversation

@yaakov-stein
Copy link

Adding support for empty sets based on #386. (Note: As of now, this is slightly different than the behavior defined in #386 - instead of removing just the matcher, the entire rule is removed to keep the semantics of the ruleset the same. I added more details in the comment there, but of course happy to switch this to the original plan.)

Previously, having any matcher with an empty set caused an error and the entire ruleset was rejected. Now, we treat the matcher with an empty set as a no-op (always false) and remove any rule that contains a matcher with an empty set (as the rule would always evaluate to false). We alert the user to this by sending a warning for each rule that will be ignored.

Test Plan:

  • Unit tests for new functionality in bf_chain_new
  • e2e tests creating rulesets with empty sets
  • Manual testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant