Issue with reference when refContent is not of type date

[edunfq]

Problem Description

I am encountering issues when using the reference type in configurations where the refContent generator is not of type date. Specifically, when refContent uses generators like enum, constant, or int with min and max, the following problems occur:

1. Field duplication behavior: In the generated JSON, the referenced field appears duplicated with the same value, while the original field name disappears.

2. Validation failure: Sometimes, the system throws an error claiming that refContent is empty, even though it is properly defined.

Minimal Reproducible Example

Input Configuration

Configuration file sent to mgodatagen:

{
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "Reference Issue Example",
    "type": "object",
    "content": {
        "originalField": {
            "type": "reference",
             "id": 1
        },
        "referencedField": {
            "type": "reference",
            "id": 1,
            "refContent": {
                "type": "constant",
                "constVal": "ConstantValue"
            }
        }
    }
}

Expected Output

{
    "originalField": "ConstantValue",
    "referencedField": "ConstantValue"
}

Actual Output

{
    "referencedField": "ConstantValue",
    "referencedField": "ConstantValue"
}

Observed Errors

When refContent is not of type date, mgodatagen produces the following error in some cases:

Error: invalid generator for field 'referencedField'
cause: 'refContent' can't be null or empty

In other cases, the generated JSON contains a duplicated field, and the original field is missing.