Consider YAML as template format

[natenho]

Is your feature request related to a problem? Please describe.
To use the scripting engine on mock templates, most of times there is a need to write an invalid JSON structure, like this:

{
  "request": {
	"method": "PUT",
	"route": "customers/{id}"
  },
  "response": {
	"status": "OK",
	"body": {
	  "url": "<#= Request.Url?.ToString() #>",
	  "customerId": "<#= Request.Route["id"]?.ToString() #>",
	  "acceptHeader": "<#= Request.Header["Content-Type"]?.ToString() #>",
	  "queryString": "<#= Request.Query["dummy"]?.ToString() #>",
	  "requestBodyAttribute": "<#= Request.Body["address"]?[0]?.ToString() #>"
	},
        "indented": false
  }
}

Describe the solution you'd like
YAML seems to be suitable alternative to write templates with C# scripts, as it is more permissive on content, like the example bellow, which is a completely valid YAML:

---
request:
  method: PUT
  route: customers/{id}
  
response:
  status: OK
  body: |
    {
      "url": "<#= Request.Url?.ToString() #>",
      "customerId": "<#= Request.Route["id"]?.ToString() #>",
      "acceptHeader": "<#= Request.Header["Content-Type"]?.ToString() #>",
      "queryString": "<#= Request.Query["dummy"]?.ToString() #>",
      "requestBodyAttribute": "<#= Request.Body["address"]?[0]?.ToString() #>"
    }
  indented: false

There is a C# implementation: YamlDotNet

Describe alternatives you've considered
To use mustache or handlebars templating alternatives would require a DSL to be created. This alternative is not suitable for Mockaco as its proposal is to reduce the learning curve, keeping C# as the scripting language.

Additional context
There are some disadvantages using YAML:

• It's not so easy to find a YAML formatter (this one is good)
• You can't use tabs to indent the file (😔)
• YAML syntax has more nuances than JSON
• There is no C# project implementing YAML 1.2 spec

[tkrafael]

I think we should stick to Razor for templating as it is almost native to aspnet core.

[natenho]

Hey, it's actually a nice idea! I'll take a closer look on this possiblity as it would be better aligned with Mockaco's proposal instead of YAML format, which I've been resistant to embrace, to be honest. I would appreciate if you could provide more details, maybe some kind of template examples of how your approach would look like.
Thanks!!