Users should be defining simple rules where possible. We don't want 7 nested not conditions. In cases where a property is effectively ignored or something could be written in a simpler way, maybe it would be useful to surface some sort of error message?
Examples I can think of:
- If a rule defines
or/xor/and together, only one of those paths will actually be evaluated
Users should be defining simple rules where possible. We don't want 7 nested
notconditions. In cases where a property is effectively ignored or something could be written in a simpler way, maybe it would be useful to surface some sort of error message?Examples I can think of:
or/xor/andtogether, only one of those paths will actually be evaluated