EddyLuten
commented
2 years ago Hi @marcemv90, thanks for reporting this. You're right, I certainly didn't foresee this use case, and it's a bug that needs to be addressed.
I wonder if aliases should be allowed within fenced code blocks since any other Markdown syntax doesn't work there either. Although technically, this plugin isn't extending Markdown and processes the page before the Markdown is parsed in MkDocs, it certainly appears as an extension of Markdown while using it.
I think you're right that a kind of escape sequence is needed.
Another bug your example exposes is that the internal regex to find aliases matches spaces within the brackets, which isn't a valid use case.
Thanks for reporting the bug, and I'll include a fix/workaround for this in the next minor release. Also, thanks for using the plugin! It's always nice to see real people other than myself using it!
marcemv90
Hello 👋
First of all congratulations for the great plugin, I find it very useful. But now I'm facing something that maybe wasn't taken into account when the plugin was developed, or maybe I'm doing something wrong. I hope somebody can shed some light over this.
The issue happens when I want to put literally
[[ something ]], enclosed by double square brackets inside a code block.Specifically, I want to put a code block with something like:
which renders just fine in Markdown, but the MKDocs console prints it as a warning because the double square brackets are interpreted as an alias that doesn't exist.
I know it can be legit using aliases within code blocks, in fact I use them, but just wondering if there could be a way to force escaping them, so they are not interpreted as an alias. As said, this is not a big deal, as the website renders good, it is just to avoid that WARNING message in the console log.
Great job with the plugin! 💪
Thanks and regards.