-
-
Notifications
You must be signed in to change notification settings - Fork 624
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
escaped ]
not working outside the playground
#2201
Comments
Jep, that's really weird |
]
don't work outside the playground]
not working outside the playground
Ok... Docus was updated with #2181 and the Nuxt Content Website now displays it correctly... See https://content.nuxtjs.org/get-started#render-pages It didn't work, when I tried updating it locally... 🤷 |
If Any ideas? |
I updated my local repo to the latest commit (including the dependency updates), and it does still not work locally... Added the What is the difference between the local environment and the one of the published site? |
Have you remove the content cached? In the .nuxt folder? |
Removed Edit: Okay... Didn't expect stuff outside the Thanks ❤️ Works fine now locally, styles loading correctly again, filename is parsed as expected. |
In conclusion, I don't see any reason why this fails for All the problems I had were because of:
and both are now resolved |
Closing this, as it seems to work correctly everywhere (excluding the nuxt.com preview) |
Environment
Web
Reproduction
https://content.nuxtjs.org/get-started#render-pages
Describe the bug
The escaped
]
don't work outside the playground (/ tests)I even tried it locally on the docs with the latest Docus version v1.14.4 which includes the escape parsing, but it always splits after the first
]
even though there is an escape character.It even displays it. It seems to ignore the rule to match
\]
before[^\]]
https://github.com/nuxt/content/pull/2169/files#diff-fd60d817a96ebccaa6b1456127b1e4589b3e10487ddb84362ab6e41ab1ede143R23
Maybe there is a missing escape in the regex.
See the extra
\
before the first]
Does not seem to change anything, still, it would be better to escape that properly... (But should also not matter 'cause it's not in a character class)
Perhaps the docs' markdown is read differently than the test and playground one?
Additional context
This is a follow-up to PR #2169
Logs
No response
The text was updated successfully, but these errors were encountered: