-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DMN configuration improvements #4282
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4282 +/- ##
=======================================
Coverage 96.12% 96.12%
=======================================
Files 730 730
Lines 23502 23502
Branches 2757 2757
=======================================
Hits 22591 22591
Misses 645 645
Partials 266 266 ☔ View full report in Codecov by Sentry. |
1a926be
to
0306362
Compare
0306362
to
70e51dc
Compare
The input expressions require additional parsing to properly extract the required input variables for a decision table.
This should help form builders configure DMN tables to see which input expressions are expected by the decision engine.
Input expressions can be complex with the actual requested variable buried deep inside. We leverage the 'feelin' library to parse FEEL expressions so that we can extract the actual (likely) expected variables and combine this information with our retrieved input clauses. This result is used to build a list of DMN variables for input mapping - this list is ordered to put labeled literal variables at the top, followed by the extracted unlabeled variables, and finally the legal identifiers that are labeled but likely complex/edge cases. This implements the DMN 1.3 FEEL identifier specification to select candidates.
Use the existing VariableSelection component to render a dropdown of available Open Forms variables. Added an accessible label to the dropdowns in the mapping tables.
Updated the assertions for the existing stories so that the interaction tests pass again. Added a story for the complex expression cases.
This has the correct input dependency resolution implementation.
70e51dc
to
e8d591b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only have to mention a small thing concerning the styling. Other than that I can't find something weird as far as I can say concerning DMN.
|
||
@include bem.element('mapping') { | ||
display: flex; | ||
flex-direction: column; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed it too while developing - I think it may be because of some pages in the admin loading additional stylesheets (bootstrap) that aren't included in Storybook.
Backported to 2.6.x with 116214c |
Closes #4269
Changes
Checklist
Check off the items that are completed or not relevant.
Impact on features
Release management
I have updated the translations assets (you do NOT need to provide translations)
./bin/makemessages.sh
./bin/compilemessages_js.sh
Commit hygiene