Philipp Ossler

Results 158 issues of Philipp Ossler

## Description This is a proof-of-concept (PoC) to see how we could import decisions and BKMs from another DMN file. The general idea: - Store parsed decisions/BKMs in a repository....

I can import other decisions from another DMN file. I can evaluate these decisions with the given import name as a prefix. --- (DMN 1.4, section 6.3.3, page 34) ![image](https://user-images.githubusercontent.com/4305769/219311521-fa5016a7-3de8-472a-9044-b9c2d7a4fbaf.png)

enhancement

**Description** Create a new benchmark and cover some basic functions. It should be a starting point to compare the DMN engines and give an idea of the performance. We can...

**Description** We should split the packages to make it clear which parts belongs to the public API. For the public API, we need to guarantee backward compatibility. * create a...

## Description Remco created a builder API for DMN that could be very useful for the tests. Currently, the code is in this repo: https://github.com/remcowesterhoud/dmn-builder-api

enhancement

**Is your feature request related to a problem? Please describe.** As a user, I want to see which rule of the decision table matched. For example, the 1st and 3rd...

enhancement

**Description** The DMN engine uses a value mapper and a function provider to build the internal FEEL engine. Currently, the value mapper and the function provider are loaded via Java's...

enhancement

**Description** Create a small REPL. The goal is to have a nice get-started experience and an easy way for testing. It could look similar to https://camunda.github.io/feel-scala/docs/reference/#feel-repl

**Description** Update the project README. The relevant data should move to the docs. The README could look similar to https://github.com/camunda/feel-scala blocked by #113

**Description** Write a guide for users to cover: * which DMN elements are supported * which parts of each DMN element are supported * how to use required decisions *...