[
https://issues.apache.org/jira/browse/JEXL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-264:
-------------------------------
Description:
Since a Jexl context may be backed by a map that is not under Jexl's control,
it may happen that keys in such a map contains spaces (quotes, backquotes).
Scripting these top-level variables is then not very easy; adding an escaping
mechanism in the syntax for top-level identifiers is provably convenient in
this case.
For example:In a script, {code}My \Variable{code} will allow accessing the top
level variable keyed with the string {code}My Variable{code}.
was:
Since a Jexl context may be backed by a map that is not under Jexl's control,
it may happen that keys in such a map contains spaces (quotes, backquotes).
Scripting these top-level variables is then not very easy; adding an escaping
mechanism in the syntax for top-level identifiers is provably convenient in
this case.
> Allow space, quote & double-quote in identifiers
> ------------------------------------------------
>
> Key: JEXL-264
> URL: https://issues.apache.org/jira/browse/JEXL-264
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 3.1
> Reporter: Henri Biestro
> Assignee: Henri Biestro
> Priority: Minor
> Fix For: 3.2
>
>
> Since a Jexl context may be backed by a map that is not under Jexl's control,
> it may happen that keys in such a map contains spaces (quotes, backquotes).
> Scripting these top-level variables is then not very easy; adding an escaping
> mechanism in the syntax for top-level identifiers is provably convenient in
> this case.
> For example:In a script, {code}My \Variable{code} will allow accessing the
> top level variable keyed with the string {code}My Variable{code}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
