New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inline double curly escaping inside a paragraph #853
Comments
@diegoperini I see the doc of Vue.js using {% raw %}{% endraw %} to escape inline double curly. I tried it in the latest version of Vuepress(1.0.0-alpha.11) but it doesn't work. I think they might add it to the stable version. |
The problem is that
|
Is there anyway to get this to work? We are running into this issue and it would be a deal breaker for us :( |
Why not try ::: v-pre
| Example |
|:----------|
| `'{{ example }}'`|
::: or
? |
We are having to do |
@SimeonRoss Have you tried the first solution? |
The only thing that works for us at the moment is: however that makes our docs markup quite wordy when double curlys are everywhere our docs. It would be nice if there was a nicer, shorter way to escape them or a way to tel Vue not to interprete them. |
@SimeonRoss Are you using the latest version of VuePress? I have test with the first solution, and it works well. |
The table format? I'm using 0.14.4 |
I used the |
Feature request
It is currently not possible to escape
{{ }}
without breaking the paragraph. It hurts the ability to write docs for template languages.What problem does this feature solve?
Assuming a template like Jinja, Handlebar.js used VuePress for documentation, they currently wouldn't be able to show inline examples.
What does the proposed API look like?
I'm not an expert on this so I don't have a strong proposition on what to choose here. Something like
\{{{ \}}}
would work I guess.How should this be implemented in your opinion?
We already have
::: v-pre
, so it should work the same.Are you willing to work on this yourself?**
I don't think I'm fluent enough in VuePress codebase to be able to implement this.
The text was updated successfully, but these errors were encountered: