Brackets and parentheses sometimes identified as unresolved/unused link ref or invalid internal link

[rmscode]

Context

I have observed this when a code fence is nested in a list.

Bug description

This is an interesting one! I tried to be as extensive as possible.

There are certain conditions that trigger Zensical Studio to report brackets or parentheses as a problem, but only when they are within a code fence that is nested in a list. I gave many examples in my reproduction. It is best to have a look.

Related links

• Report a bug

Reproduction

reproduction.zip

Steps to reproduce

New profile in VS Code with only the Zensical Studio extension installed.

Steps are in the reproduction.

Editor

Visual Studio Code

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues.
• I have attached a .zip file with a minimal reproduction.
• I have read and accepted the Zensicals Terms of Service and the Zensical Studio End User License Agreement.

[squidfunk]

Thanks for the reproduction and taking the time to investigate and provide not only one but several reproductions! This helps us massively to find the remaining edge cases in our lossless Python Markdown parser ☺️ Looking into it.

[squidfunk]

Fixed. This was a real parity gap, specifically around fenced code blocks with blank lines in lists. This is handled by SuperFences in Python Markdown, which jumps through many hoops to get indentation right. All provided cases work now - I've added rust to just signal that all of those are now correctly parsed as fenced code blocks.

I'll let you know when we publish the next release, shouldn't be long ☺️

[squidfunk]

The fixes have been released as part of Zensical Studio 0.1.3. Please let us know if you encounter anything else!