Recursive sample generation

[leflings]

Fixes #1560

This PR modifies SampleJsonDataGenerator to support re-use of definitions, and by extension, recursion.

See issue for the problem before.

Example 1

Now the following schema:

{
    "definitions": {
        "withNumber": {
            "type": "object",
            "required": ["value"],
            "properties": {
                "value": {
                    "type": "number"
                }
            }
        }
    },
    "type": "object",
    "required": ["number1", "number2"],
    "properties": {
        "number1": { "$ref": "#/definitions/withNumber" },
        "number2": { "$ref": "#/definitions/withNumber" }
    }
}

generates

{
  "number1": {
    "value": 0.0
  },
  "number2": {
    "value": 0.0
  }
}

Example 2

Schema:

{
    "definitions": {
        "data": {
            "type": "object",
            "required": ["body"],
            "properties": {
                "body": { "$ref": "#/definitions/data" }
            }
        }
    },
    "type": "object",
    "required": ["data"],
    "properties": {
        "data": { "$ref": "#/definitions/data" },
    }
}

generates:

{
  "data": {
    "body": {
      "body": {
        "body": null
      }
    }
  }
}

The level of recursion is controlled by a new setting on SampleJsonDataGeneratorSettings

[lahma]

doesn't this kill performance? capturing lambda and used inside recursion, having O(n) characteristics?

[leflings]

I would be very surprised if people use this functionality in performance sensitive scenarios. It's easy to rewrite this without the use of a capturing lambda if you deem this to be a big performance issue

[lahma]

Ah true, this is only for sample data indeed. Anything called by NSwag in normal generation process usually is quite performance sensitive.