OperatorRule and ExpressionRule #262
johnf-jade
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Was any consideration given to modelling these two distinct types of Rule with different classes with a common abstract Rule base class? Then an OperatorRule could have Operator and child Rules, while ExpressionRule has neither but has Expression instead. Then there wouldn't be a need to validate that these properties are mutually exclusive and it might make the intention more discoverable to consumers.
Beta Was this translation helpful? Give feedback.
All reactions