alishaaaqil opened a new issue, #7229:
URL: https://github.com/apache/incubator-kie/issues/7229
### Describe the bug
A DMN decision with a collection result type returns a nested list when a
`for` expression returns a Context containing a single value per iteration.
For example, the result is `[["aa"], ["bb"], ["cc"]]` instead of `["aa",
"bb", "cc"]`. This can cause downstream filtering to return an empty list.
### Expected behavior
The decision should return a flat list:
```feel
["aa", "bb", "cc"]
```
### Actual behavior
The decision returns a list of singleton lists:
```feel
[["aa"], ["bb"], ["cc"]]
```
Downstream filtering consequently returns an empty list.
### How to Reproduce?
Create a DMN decision with a collection result type and a `for` expression
that returns a Context entry containing one value per iteration.
For example, the intended logic is equivalent to:
```feel
for x in ["a", "b", "c"]
return { value: x }.value
```
Evaluate the decision and inspect its result. The values are unexpectedly
wrapped in individual lists rather than returned as a flat list.
### Output of `uname -a` or `ver`
_No response_
### Output of `java -version`
_No response_
### GraalVM version (if different from Java)
_No response_
### Kogito version or git rev (or at least Quarkus version if you are using
Kogito via Quarkus platform BOM)
_No response_
### Build tool (ie. output of `mvnw --version` or `gradlew --version`)
_No response_
### Additional information
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
