Bug: Empty Lines Around Blockquotes Can Cause Problems with Nested Callouts with a Single Blank Line Between Them

[alitekdemir]

• Linter v1.17.0

Describe the Bug

I showed it in the video. Actually I was thinking it wouldn't add extra characters. Since I did not see such an explanation in the document, I wanted to report it as an error.

Expected Behavior

shouldn't add extra characters.

i use this sample markdown

> [!multi-column]
>
>> [!note]+ Use Case
>> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
>> ##### User Case Background
>> Vitae nunc sed velit dignissim sodales. In cursus turpis massa tincidunt dui ut ornare lectus.
>
>> [!warning]+ Resources
>> #### Requirement
>> - Lorem ipsum dolor sit amet
>> - Vitae nunc sed velit dignissim sodales.
>> - In cursus turpis massa tincidunt dui ut ornare lectus.
>
>> [!todo]+
>> - [x] Define Use Case
>> - [ ] Craft User Story
>> - [ ] Develop draft sketches

Screenshots

Obsidian_2023-07-20_15-39-40.mp4

[pjkaufman]

@alitekdemir , I am not sure this is a bug. The Linter knows almost nothing about callouts so they are treated as blockquotes. In this case, the blank line is upgraded to be a doubly nested blank line because the blank is between 2 doubly nested blockquotes.

I can see how this would cause problems for callouts, but it should have 0 affect on true blockquotes.

I may need to add some consideration for callouts, but I will have to look more into this.

[pjkaufman]

I believe I have a fix for this. I will push it up and barring any formatting issues caused when I test before the next release, it will go out with the next release.

[pjkaufman]

Hopefully this fix will not cause other issues to pop up.

[alitekdemir]

Thank you very much for your prompt attention. And my heartfelt congratulations to you.