Replies: 1 comment 1 reply
|
Hi there! Thank you for reporting this issue. This is caused by xyOps' mustache macro expansion system we call XYEXP. All string-valued Plugin Parameters are processed for xyOps For a quick workaround, you can use different template delimiters or construct the braces at runtime, for example with If this is reusable application code that needs to contain Mustache templates naturally, creating a custom Event Plugin is the way to go. Event Plugin source code itself is not macro-processed. Note that any string parameters passed to that Plugin will still support xyOps macro expansion. Hope this helps! |
Uh oh!
There was an error while loading. Please reload this page.
Hey!
I came across some weird behaviour in an event script whereby trying to use
String.replaceorString.replaceAllon a string containing variables with mustach syntax eg {{name}} caused the output to replace every character with the replace value passed to the method.For example, the result of:
Produces:
2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010ZH2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Ze2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zl2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zl2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Z 2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Z,2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Z 2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zt2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zd2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Za2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zy2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Z 2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zi2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Zs2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010Z 2026-08-28T15:38:20.010ZB2026-08-28T15:38:20.010Zo2026-08-28T15:38:20.010Zb2026-08-28T15:38:20.010ZChanging the mustach syntax for something else fixes the issue eg. swapping the brace { for an underscore _.
We'd usually use the syntax for email templates or messages with variable content but it's not an issue to use different syntax.
All reactions