[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Jozef Marko commented on DROOLS-4994:
-------------------------------------
Could we please discuss also the text of the hints here? [~yamer] do you have any proposals?
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4994:
------------------------------------
[~uxdlc] Thank you, both solutions are fine for me. In case of a short description, I prefer the first one.
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13052) Workaround for MicroProfile Config TCK "ShouldThrowException" failure
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-13052?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFLY-13052:
-------------------------------
Summary: Workaround for MicroProfile Config TCK "ShouldThrowException" failure (was: Workaround MicroProfile Config TCK "ShouldThrowException" failure)
> Workaround for MicroProfile Config TCK "ShouldThrowException" failure
> ---------------------------------------------------------------------
>
> Key: WFLY-13052
> URL: https://issues.redhat.com/browse/WFLY-13052
> Project: WildFly
> Issue Type: Component Upgrade
> Components: MP Config
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class).
> Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type.
> This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13052) Workaround MicroProfile Config TCK "ShouldThrowException" failure
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-13052:
----------------------------------
Summary: Workaround MicroProfile Config TCK "ShouldThrowException" failure
Key: WFLY-13052
URL: https://issues.redhat.com/browse/WFLY-13052
Project: WildFly
Issue Type: Component Upgrade
Components: MP Config
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class).
Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type.
This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5002:
--------------------------------
Steps to Reproduce:
# Create structure like
## !Screenshot from 2020-02-04 07-50-43.png|thumbnail!
# Click plus next to *tIllness*
## !Screenshot from 2020-02-04 07-50-53.png|thumbnail!
Current: *Medicine* field is expanded
Expected: *Medicine* field remains collapsed
> [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-5002
> URL: https://issues.redhat.com/browse/DROOLS-5002
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png
>
>
> Issue found during DROOLS-4485 review.
> When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months