[JBoss JIRA] (DROOLS-2263) [GSS] (6.4.z) Unexpected results in GDST when using enumerations with commas
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2263?page=com.atlassian.jira.plugi... ]
Toni Rikkola moved RHBRMS-3064 to DROOLS-2263:
----------------------------------------------
Project: Drools (was: JBoss BRMS Platform)
Key: DROOLS-2263 (was: RHBRMS-3064)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Decision Table Editor
(was: Business Central)
Affects Version/s: (was: 6.4.1.GA)
QE Status: NEW
> [GSS] (6.4.z) Unexpected results in GDST when using enumerations with commas
> ----------------------------------------------------------------------------
>
> Key: DROOLS-2263
> URL: https://issues.jboss.org/browse/DROOLS-2263
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
>
> When using enumerations where the values itself contain a comma, the rules generated by a GDST are unexpected, as the "contains in" operator splits those values in the enumerations. Example enumeration:
> {noformat}
> fact: person
> field: city
> context: ['paris','london','new york,boston']
> {noformat}
> Note: see the 'new york, boston' sample.
> The code generated will be:
> {noformat}
> rule "Row 1 personGDT"
> dialect "mvel"
> when
> p : person( city in ( "new york", "boston" ) )
> then
> end
> {noformat}
> Basically "paris" and "new york,boston" will be treated by the DSL parser as 3 strings in the DRL generation and will produce someting simiular to
> p : person( city in ( "paris", "new york", "boston" ) )
> But what the customer expects is the following
> p : person( city in ( "paris", "new york,boston" ) )
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3537) Add support for testing of CLI multi page output
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3537?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3537:
----------------------------------------------
In order to emulate an interactive session, we plan to add some test only methods:
ReadlineConsole
public boolean isPagingOutputEnabled()
public void forcePagingOutput(boolean forcePaging)
Console is made available through CommandContextImpl: ReadlineConsole getConsole()
> Add support for testing of CLI multi page output
> ------------------------------------------------
>
> Key: WFCORE-3537
> URL: https://issues.jboss.org/browse/WFCORE-3537
> Project: WildFly Core
> Issue Type: Task
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> For testing of WFCORE-426 feature, it would help to have a method which forces paging of output even if the CLI does not run in system terminal.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3538) Improve test coverage of WFCORE-426
by Erich Duda (JIRA)
Erich Duda created WFCORE-3538:
----------------------------------
Summary: Improve test coverage of WFCORE-426
Key: WFCORE-3538
URL: https://issues.jboss.org/browse/WFCORE-3538
Project: WildFly Core
Issue Type: Task
Components: CLI
Affects Versions: 4.0.0.Alpha6
Reporter: Erich Duda
Assignee: Erich Duda
There should be automatic tests which verifies that long output is paged and that CLI reacts on keys SPACE, ENTER, KEY DOWN.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3537) Add support for testing of CLI multi page output
by Erich Duda (JIRA)
Erich Duda created WFCORE-3537:
----------------------------------
Summary: Add support for testing of CLI multi page output
Key: WFCORE-3537
URL: https://issues.jboss.org/browse/WFCORE-3537
Project: WildFly Core
Issue Type: Task
Components: CLI
Affects Versions: 4.0.0.Alpha6
Reporter: Erich Duda
Assignee: Jean-Francois Denise
For testing of WFCORE-426 feature, it would help to have a method which forces paging of output even if the CLI does not run in system terminal.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2261) [DMN Designer] Context Entry Default Value Column width does not fill parent
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2261?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-2261:
----------------------------------------
my 2c, I would keep simple and not store more than necessary, unless DMN1.2 specify it.
Moreover on our side I canNOT store width of column because they don't receive DMN IDs.
If the UI can auto-size to a sensible degree, it would be preferable I think.
> [DMN Designer] Context Entry Default Value Column width does not fill parent
> ----------------------------------------------------------------------------
>
> Key: DROOLS-2261
> URL: https://issues.jboss.org/browse/DROOLS-2261
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Attachments: after-reopen.png, non-saved.png
>
>
> Context Entry Default Value Column width does not fill parent. Width is fixed if some small resizing is done in grid.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months