Template-including-parent:: false messes up Markdown file

I have noticed that having a template with “template-including-parent:: false” would work OK in Logseq as rendering goes but the Markdown file is wrong as the first block still maintains the bullet (the dash in Markdown) and all other indentations keep the same even if their parent block (which lost its “dash”) have been de-dented:

How to reproduce:

- template:: test
  template-including-parent:: false
	- # some h1
		- some correctly indented text;
		- some correctly indented text;
	- # some other h1
		- ## some h2
			- some correctly indented text;
			- ### some h3
				- some correctly indented text;
			- some correctly indented text;

Upon applying the template:

, which looks ok in Logseq, but in the Markdown I have this:

- # some h1
	- some correctly indented text;
	- some correctly indented text;
# some other h1
	- ## some h2
		- some correctly indented text;
		- ### some h3
			- some correctly indented text;
		- some correctly indented text;

and in VSCodium:

Problems:

  1. “- # some h1” should miss the “-” in front of it;
  2. when parent disapears, all lines should De-Dent, not only the Parent Bullets, by one Tab. It is clearly not the case;

With the above corrected, one would have proper Markdown Rendering:

What comes to mind is that, if this would work correctly, having such property for Blocks (“including-parent:: false”) would render bullet-less Markdown when Zoomed In on the Parent-Bullet and then exporting the rendered content would produce correct Markdown.

I am using Logseq-win-x64-0.9.10-full.

Interesting.
Seems to be specific to headers of any size.
Regular text works fine.

PS. This worked fine in older versions. I don’t know which introduced this problem. However I have a template for references which utilizes a similar template model and older pages have the proper structure while newer are missing those -.

Do these Bug Reports work on Votes? If so, please Vote if you are experiencing the bug.

So far I have only tested with Headers (regular text works ok, I confirm).

Bug reports generally are handled in GitHub actually.
They have a template for it there.
Not sure why there is still a section for it here though.

You’ll need an account for it though.

:man_facepalming:

That’s a shame… there should be some linking between these platforms so that we don’t have to duplicate our bug-reports. It takes time to do these and it’s disconcerting to learn that they’re in vane :frowning: