goldmansachs / jdmn Goto Github PK

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Fields should be declared final if not set outside constructor..

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

All input parameters should be inputs.

Actual Behavior

Only root package is a parameter.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Imports should be organised.

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

testCases.xsd should be in main folder

Actual Behavior

testCases.xsd is in the test folder

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Remove comment

/**

• Created by ...
  */

from Java classes.

Expected Behavior

The comments should contain the name of the decision.

Actual Behavior

The comments do not contain the name of the decision.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Add extra tests and and rename it.

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Apply method should invoke evaluate()

Actual Behavior

Evaluate is inlined inside apply.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Less CL2 redundant tests in dmn-core

Actual Behavior

Duplicated in dmn-tck-integration-tests

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Less CL3 redundant tests in dmn-core

Actual Behavior

Duplicated in dmn-tck-integration-tests

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Test folders should match the name of the transformer.

Actual Behavior

Name of transformer is SimpleName, folder name is java.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

If decision tables are sparse, children should be evaluated on demand.

Actual Behavior

All children are evaluated

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Same name for the variables, resolve them via this

Actual Behavior

Different variables. For example, decision and decisionOutput

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

All Interpreter tests are in the dmn-tck-integration-tests

Actual Behavior

The Interpreter tests are in dmn-core

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

User should be able to configure the sparsity threshold

Actual Behavior

Lazy evaluation is applied to all decision tables.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Add extra tests and rename the existing one.

Expected Behavior

The maven plugin should display the sparse decisions and the decisions to be lazy evaluated

Actual Behavior

None is displayed.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

No NC TCK unit tests.

Actual Behavior

Test cases for NC TCK in dmn-core

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Template providers should be injected in the transformers

Actual Behavior

Template providers are part of the dialects

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Not NPE when TDefinitions is empty

Actual Behavior

NPE when TDefinitions is empty

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

All tests should be in the same package with the class under test

Actual Behavior

The tests are in a different package.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

DAG template provider should support lazy evaluation.

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

There should be common folder for templates.
There should be a folder for specific templates

Actual Behavior

All templates are in the same folder

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

All modules should be clean according to cleanup action in Intellij

Actual Behavior

Modules are not clean.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Missing integration test for DAG template provider and lazy evaluation

Actual Behavior

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Should be able to choose variants based on the mapping of FEEL types to Java types

Actual Behavior

One single mapping is available.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

All decisions should implement com.gs.dmn.runtime.DMNDecision

Actual Behavior

It's missing.

jDMN Version where this issue was observed

1.0.0-SNAPSHOT

Steps to reproduce the behavior

Expected Behavior

User should be able to specify several transformers to be executed in sequence

Actual Behavior

Only one is allowed

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Expected Behavior

Avoid duplicate execution of decisions

Actual Behavior

Some decisions in the decision model are executed several times.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior

Trace the execution of 0004-lending.dmn

Expected Behavior

Generated code should compile.

Actual Behavior

Compilation fails when output ia lazy evaluated.

jDMN Version where this issue was observed

1.0.0

Steps to reproduce the behavior