[Bug] Error in YAML front matter preview

[sebastian-rand]

Description

I saw this issue was raised already but closed because the original poster did not provide examples.

It seems that the preview mode does not respect multiline strings, and instead puts them all on one line. This happens both when using the pipe and when using the right angle bracket character (which is supposed to enable newlines with a blank line, according to the spec as outlined here).

Sample Markdown

---

title:
summary: |
This is line one.
This is a new line.
So is this.

---

---

title: Example using right angle bracket
summary: >
This is line one.

This is a new line after a blank line.

So is this.

---

MarkEdit Version

1.33.0 (92)

MarkEdit Preview Version

1.8.1

macOS Version

Tahoe 26.5.1

[cyanzhong]

Thanks for providing the examples.

I can "repro" the issue as you mentioned, exactly the same result. If we are talking about "YAML".

However when the question comes to "front-matter", I am not sure if it really supports multiple lines rendering (parsing is fine here, obviously).

Here is how GitHub.com renders it:

Here is a discussion: https://talk.jekyllrb.com/t/specifying-multiline-front-matter/2896/2

I couldn't find a well-known implementation that I can try online to validate this, nor something I trust as the "spec".

[sebastian-rand]

Thanks for checking it out! I should note at the start that I am not a programmer/engineer and may be missing what your response is really saying. Perhaps I am confusing the specification of YAML with the specification of front-matter. My assumption was that if the previewer recognizes front-matter as following YAML syntax, and renders that front-matter in a way that shows that it's somehow different from the rest of the markdown document (which it does, by putting it in a table), then ideally it would preserve things like line breaks when YAML provides a mechanism for encoding line breaks. But maybe the table format itself makes that hard/impossible; some apps (e.g., mweb) just render the YAML header as a code block, perhaps that's why.

Anyway, keep up the good work!

[cyanzhong]

I will close this for now unless we have a clearer understanding of how this "should" work.

Anyway, aligning with GitHub.com isn't a bad thing since the styling we use is already GitHub.

Thanks for the feedback.