ini-parser VS YamlDotNet

Hi for all, thanks for your suggestion and advises, after all consideration i have decided to stick to ini file format and using this lib ini-file-parser my template look like this: example for 4 Tests.

If the duplicate keys are in different sections I believe this lib should handle them just fine: https://github.com/rickyah/ini-parser

Alternatively, instead of using a type provider (which isn't simple by any means), you can use any number of CSV or INI parsers, e.g. https://joshclose.github.io/CsvHelper/ or https://github.com/rickyah/ini-parser

When it comes to YAML serialization and deserialization in .NET, YamlDotNet is a go-to library with over 100 million downloads on NuGet. It is also integrated into various projects by Microsoft and the .NET team, despite the absence of an official Microsoft YAML library for .NET.

Looking at the sample, it doesn’t look like navigation the ‘representation model’ is that much different from doing the same for a JSON document. I suggest trying to make that work.

If you don't want the jank, YAML supports comments. https://github.com/aaubry/YamlDotNet can read commented files just fine, and can probably emit them as well with some custom handling code.

I think you should provide your input here, if you haven't already.

In the past I've used DotNetYaml for this. This library allows you to serialize and deserialize between YAML and your own objects.

The frontmatter string needs to be deserialised to a strongly-typed FrontMatter instance, using the YamlDotNet library. Then, change the Published value to true.