How to escape the expressions ${myVar} in a engine template ? about engine

[jonschlinkert]

We can update the regex to allow templates to be escaped. However, if you need to render those escaped templates at some other point in the process, you will need to unescape them first. I'll take a look at the regex and see what needs to be done.

[jonschlinkert]

I believe you should be able to escape the template by doing \${foo}. I'm not sure if that will work, let us know either way and we'll go from there.

(fwiw, I get all of the notifications from GitHub, feel free to tweet as well, but it's just a duplicate notif to me. I saw a bunch of the notifs while I was on vacation, I'm back now. Sorry for the delay)

edit: btw this template-escaping issue has been one of the most frustrating aspects of doing these templating libraries. there are so many scenarios like this where different syntaxes collide in some way, or where users need to do documentation for templates but they don't want the templates inside markdown fences to be rendered, etc. There are several ways we can work around this, I just need to know more about your build and if that suggestion I gave worked.

[rbecheras]

Hi Jon!

Sorry for the duplicated notifications, it's noticed, github notifications are fine.

Sorry too I forgot to mention I already tried \${foo} and it don't work, it behave exactly like ${foo} .

[rbecheras]

Hi Jon,

For now I use a workaround but let me know what you think about it:

• PR: sirap-group/generate-swap-project#80
• Workaround commits:
  • sirap-group/generate-swap-project@c8ab358
  • sirap-group/generate-swap-project@6b552dc
• Passing tests: https://travis-ci.org/rbecheras/generate-swap-project/builds/327214195?utm_source=github_status&utm_medium=notification