[
https://issues.apache.org/jira/browse/VELOCITY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-845.
-----------------------------------
Resolution: Won't Fix
Assignee: Claude Brisson
Fix Version/s: 2.x
I agree that it could be a nice feature. The day Velocity uses its own parser,
it may be possible. But for now we're using Javacc, which doesn't allow such
customization.
On the other hand, it is definitely doable at compile time in the Javacc source
file (and a few other places in parser/nodes).
Nevertheless, *most* of the time, Velocity and jquery code cope pretty well
together, Velocity leaving aside $vars that don't exist in the context. When a
problem occurs, you still have escaping: just prefix the reference with a
backslash.
> User Defined Character Replacement for the "$" Sign.
> ----------------------------------------------------
>
> Key: VELOCITY-845
> URL: https://issues.apache.org/jira/browse/VELOCITY-845
> Project: Velocity
> Issue Type: New Feature
> Components: Engine
> Affects Versions: 1.7
> Reporter: Werner Fischer
> Assignee: Claude Brisson
> Fix For: 2.x
>
>
> Would be of huge help if Velocity would allow the users to define a character
> replacement for the "$" sign, e.g. using the velocity properties:
> http://velocity.apache.org/engine/releases/velocity-1.7/developer-guide.html#Velocity_Configuration_Keys_and_Values
> with a new one like:
> variable.sign.redefine=€
> The $ sign is a good default for many situations, but it's very bad for web
> stuff and JavaScript code. Escaping could be avoided by allowing the user to
> use something else.
> tnx.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
