Releases: camunda/feel-scala
Releases · camunda/feel-scala
1.12.0
Changelog
- new temporal functions: now() + today() (#175)
- new temporal builtin functions from DMN 1.3 (#182)
- extend decimal() function by optional parameter for rounding mode (#165) (thanks to @bigpuritz)
- fix comparing null with not existing variable (#176)
- fix that variable names can contain a key-word (#179)
1.11.2
1.11.0
Changelog
-
access an item of a list by providing a variable as index (#80)
-
disable external functions by default (#116)
-
Maven group-id changed from
org.camunda.bpm.extension.feel.scala
toorg.camunda.feel
(#79). The FEEL engine is now available under:<dependency> <groupId>org.camunda.feel</groupId> <artifactId>feel-engine</artifactId> </dependency>
-
Camunda integration modules (
feel-engine-factory
,feel-engine-plugin
,feel-engine-spin
) moved to thecamunda-bpm-platform
repository (#78) -
change package structure to reflect public/private API (#91)
1.10.1
1.10.0
Features
- support multiple
ValueMappers
- value mappers do not have to extend each other anymore
- precedence can be configured by providing a priority
- optional Camunda Spin dependency by extracting the value mapper into its own module
Migration
- if Camunda Spin types are used
- add a dependency to
feel-camunda-spin
in your POM or include the new JAR
- add a dependency to
- if a context is used to evaluate an expression via engine API
- use
CustomContext
instead ofRootContext
- use
- if
CustomFunctionProvider
is implemented- add
functionNames
method and return all available function names
- add
- if
ValueProvider
is implemented- add
keys
method and return all available variable names - (optional) return variables as raw objects instead of FEEL types
- add
- if
CustomValueMapper
is implemented- adjust transform methods to pass a function to transform the inner values of a collection type
- use
Context.StaticContext
instead ofDefaultContext
for collection types - (optional) override
priority
field/method to change the precedence