I’m attempting to convert a port of my YAML frontmatter to JSON for my article schema, but the conversion messes with the case on my keys. Method 1 (ideal) Frontmatter title: Example Post schema: mainEntity: - "@type": Question name: What is an example question? acce…

[image] AlanBreck: Any thoughts on how to avoid this? Object keys in front matter are always converted to lowercase. Array elements in front matter are left as-is (you have already discovered this). You might consider placing the data in a page resource: content/ └── post/ └── test/ …

That’s a much better workaround. Thanks for the suggestion! [image] jmooring: Object keys in front matter are always converted to lowercase. Array elements in front matter are left as-is (you have already discovered this). Thoroughly out of curiosity, why is this the case?

[image] AlanBreck: why is this the case? A little history… https://discourse.gohugo.io/t/19150/11 https://discourse.gohugo.io/t/15828/3

That’s helpful background. Thank you!

Conversion to JSON from YAML messing with key casing

support

jmooring August 5, 2022, 5:47pm 4

A little history…

https://discourse.gohugo.io/t/19150/11
https://discourse.gohugo.io/t/15828/3

Topic		Replies	Views
Why is page params key lowercase? support	5	2690	December 16, 2018
Is there a way to have case-insensitive frontmatter map keys support taxonomy	2	851	August 16, 2023
How to maintain case sensitivity from frontmatter support	0	439	February 5, 2021
[SOLVED] Help interpreting a warning support	3	758	August 27, 2018
[solved] Proper way to format a array in root yaml support	11	5471	February 28, 2018

Conversion to JSON from YAML messing with key casing

Related topics