[
https://issues.apache.org/jira/browse/JEXL-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro resolved JEXL-267.
--------------------------------
Resolution: Not A Problem
Assignee: Henri Biestro
Fix Version/s: 3.1
This behavior is what is expected and has been implemented since 3.0; the
actual commit happened in 2013 (
https://github.com/apache/commons-jexl/commit/771afc52b2161d1db9859670509b73ee5e7c0b35
).
The second form allows creating a script with parameters without having to use
the explicit API.
The following commit added a test that illustrates the expected behaviours:
https://github.com/apache/commons-jexl/commit/b6c6db7c60726c1eeefe90da8506941ec1ad561b
> Lambda evaluation
> -----------------
>
> Key: JEXL-267
> URL: https://issues.apache.org/jira/browse/JEXL-267
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 3.1
> Reporter: Dmitri Blinov
> Assignee: Henri Biestro
> Priority: Major
> Fix For: 3.1
>
>
> The following script returns correct lambda {{function(s,v)\{42;}}}
> {code:java}
> var x = (s, v)->{42}{code}
> While the following script returns {{42}}
> {code:java}
> (s, v)->{42}{code}
> The expected result is the same lambda as in the first example
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
