feat: Add IS_NULL and IS_NOT_NULL operators for rule null handling #1895
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds comprehensive null handling support to Maintainerr rules, allowing users to explicitly match on null values and fixing the boolean logic bug identified in PR #1857.
Key Changes
🐛 Boolean Logic Fix
Fixed the boolean logic bug from PR #1857:
✨ New Null Operators
Added two new operators to
RulePossibility
enum:IS_NULL
(value: 18) - Matches values that are explicitlynull
IS_NOT_NULL
(value: 19) - Matches values that are notnull
🔧 Smart Processing Logic
Enhanced rule execution to allow null values for null-specific operators while preserving existing behavior:
🎯 New Rule Type
Added
RuleType.NULL
(ID: 5) specifically for null operations, ensuring type safety and proper UI integration.Use Cases
Users can now create rules like:
Testing
Backwards Compatibility
This is a non-breaking change:
Example Usage
Fixes #1894.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.