Obsidian: Front Matter Template does not publish "double quotes" to Obsidian YAML about omnivore HOT 5 OPEN

"og:image"

Yeah, that's right. We use the library provided by Obsidian to parse YAML file first to validate it and it will remove the outer quotation marks unless the value is a multiline string or some other cases

from omnivore.

I don't think that will work because what if the description has quotes in it?

from omnivore.

Fair point, although article descriptions can be manually changed in Omnivore, so as long as I change these to be YAML compliant then that shouldn't be an issue.

Would this be the reason why the quotation marks aren't being used? In data.json they are being escaped as special characters \"

from omnivore.

I don't think thats the issue, i suspect its because we validate in a YAML library and then spit out the validated YAML. But let me verify that with @sywhb

One question: why do you need the quotes? Without white space isn't og:image evaluated to the same thing in YAML as "og:image" or are they treated as different properties?

from omnivore.

One question: why do you need the quotes? Without white space isn't og:image evaluated to the same thing in YAML as "og:image" or are they treated as different properties?

I think I might not actually need the double quotations. I'm publishing my vault online using Obsidian-Digital-Garden, and I'm just following the docs here on setting metatags for a page, and the example screenshot shows the aforementioned YAML lines as being surrounded by double quotes. However, I tested on Omnivore article pages which have been published on my site and the metatags all render just fine. The page I actually used as an example in my first post even works – History of Morrowind - The Unofficial Elder Scrolls Pages (UESP).

So for my specific use case, this issue is resolved. It might be useful to keep open though for any other possible use-cases where you'd want the Omnivore frontmatter template to publish double quotations.

from omnivore.