You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a Vue v3 project using custom delimiters to avoid conflicting with a (Shopify Liquid) server-side templating language that relies on handlebars {{ and }} already.
So far, my only configuration for this has been to set the option in vite.config.ts and everything seems to be working pretty much okay:
...But I notice the syntax highlighting in my component .vue files doesn't seem to be aware of the setting and couldn't see any mentions in the Vetur guide.
Maybe there's some way to work around this already that I'm missing? Or else would be nice if a configuration could be added.
For what it's worth I'm not particularly tied to the choice of "${", "}", and appreciate there might be some edge cases that make that a particularly tricky case? Like this for example combining a style binding (normal JS ${}) with a Vue template HTML substitution (Vue ${}):
Feature Request
I'm working on a Vue v3 project using custom delimiters to avoid conflicting with a (Shopify Liquid) server-side templating language that relies on handlebars
{{
and}}
already.So far, my only configuration for this has been to set the option in
vite.config.ts
and everything seems to be working pretty much okay:...But I notice the syntax highlighting in my component
.vue
files doesn't seem to be aware of the setting and couldn't see any mentions in the Vetur guide.Maybe there's some way to work around this already that I'm missing? Or else would be nice if a configuration could be added.
For what it's worth I'm not particularly tied to the choice of
"${", "}"
, and appreciate there might be some edge cases that make that a particularly tricky case? Like this for example combining a style binding (normal JS${}
) with a Vue template HTML substitution (Vue${}
):The text was updated successfully, but these errors were encountered: