autorest VS YamlDotNet

Doesn't autorest do that? https://github.com/Azure/autorest

The autorest project uses this actually.

It works by embedding yaml code blocks into a markdown file.

It’s actually not completely awful and has proven somewhat useful to have a configuration clearly documented within the config.

https://github.com/Azure/autorest/blob/main/docs/generate/re...

The StackQL Azure provider was created using the Autorest project using Azure specification docs from the azure-rest-api-specs repository. We will be adding integrated interactive authentication; for now, this is cli/sdk based; you can find all the documentation here.

I wonder if there is a format for API -> client automation that can be good enough, in the end Stripe have a rest API, with enough description it should be possible.

Okay so after a quick google it appears Microsoft are the "Simpsons already done it" of the programming world: https://github.com/Azure/autorest/

It'd probably be a good idea to add an Elixir backend for that and point it at Stripe's API here: https://github.com/stripe/openapi

It is definitely created with AutoRest. That's both its strength and its greatest weakness. :(

Honorable mentions: AutoRest, Visual Studio Connected Services

The Microsoft.Graph.* modules are AutoRest-generated modules. They are a straight wrapper around the REST calls that you would perform with Invoke-RestMethod or Invoke-WebRequest.

You can try autorest. I haven't used NSwag but I believe the two are similar. Also it looks like Nswag has a command line tool that you could use.

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.