[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Resolved] (JEXL-275) Allow safe navigation as option
From:       "Henri Biestro (Jira)" <jira () apache ! org>
Date:       2020-04-29 10:28:00
Message-ID: JIRA.13185543.1537195768000.64353.1588156080210 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/JEXL-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Henri Biestro resolved JEXL-275.
--------------------------------
    Resolution: Fixed

Changeset: c716d1de3fe1bde6a330629939c45745e9e65e95
Author:    henrib <henrib@apache.org>
Date:      2020-04-29 12:25
Message:   JEXL-275: strict mode is enough (wrt safe) to detect undefined vars as \
arguments

> Allow safe navigation as option
> -------------------------------
> 
> Key: JEXL-275
> URL: https://issues.apache.org/jira/browse/JEXL-275
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 3.1
> Reporter: Henri Biestro
> Assignee: Henri Biestro
> Priority: Major
> Fix For: 3.2
> 
> 
> WHAT:
> The 'safe navigation' operator (?.) - allowing a null property to stop and return \
> null in a navigation expression - has been introduced. However, in many occasions, \
> being able to let the '.' and '[...]' operators behave 'safely' without reverting \
> to the 'lenient' mode  would be very convenient. Moreover, it seems 3.1 already \
> allow 'safe' / silent navigation when calling methods / functions; fixing this \
> behaviour will break existing scripts. Explicitly introducing this 'safe' behaviour \
> would mitigate the (3.2) migration cost greatly. HOW:
> Builder option to set the flag, inject checking the flag when node.isSafeLhs(...) \
> is used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[prev in list] [next in list] [prev in thread] [next in thread]