[jboss-jira] [JBoss JIRA] (DROOLS-1791) ConditionInspectors for guided DT editor don't do checks for all allowed operators

[Michael Anstis (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Anstis moved GUVNOR-2234 to DROOLS-1791:
------------------------------------------------

        Project: Drools  (was: Guvnor)
            Key: DROOLS-1791  (was: GUVNOR-2234)
       Workflow: GIT Pull Request workflow   (was: classic default workflow)
    Component/s: Guided Decision Table Editor
                     (was: Guided Decision Table)


> ConditionInspectors for guided DT editor don't do checks for all allowed operators
> ----------------------------------------------------------------------------------
>
>                 Key: DROOLS-1791
>                 URL: https://issues.jboss.org/browse/DROOLS-1791
>             Project: Drools
>          Issue Type: Bug
>          Components: Guided Decision Table Editor
>            Reporter: Zuzka Krejčová
>            Assignee: Toni Rikkola
>            Priority: Minor
>              Labels: reported-by-qe
>
> For String fields, guided DT editor allows the following operators:
> ==, !=, <, >, <=, >=, matches, soundslike, == null, != null, in, not in
> StringConditionInspector pretty much only checks if the operator is ==, != or 'in'.
> This means that some issues won't be detected (Validation and Verification for Decision Tables). E.g. for rules/conditions like 'str > "a"' and 'str > "c"', the subsumption won't be detected (but a fact instance with str == "x" will fire both rules).
> ComparableConditionInspector checks for ==, !=, <, >, <=, >= ops, but:
> for Dates, guided DT editor allows:
> ==, !=, <, >, <=, >=, == null, != null, in, not in, after, before, coincides
> for numerical types, guided DT editor allows:
> ==, !=, <, >, <=, >=, == null, != null, in, not in



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)