Add support for string based properties decorated with the RangeAttribute

Consider the following:

public class MyModel
{
    [Required]
    [Range(1, 65535)]
    public string Port { get; set; }
}
var fixture = new Fixture();
var model = fixture.Create<MyModel>();

In 3.51.0 the first call the Create() worked, however subsequent calls threw, now in 4.0.0-rc1 (the version I am using), the first call throws ObjectCreationException whereas the attribute itself offers support for the use case.

[jcasale]

To be honest, it’s a convention I am used to from the ASP arena and I don’t know if it’s an abuse of the facility or intended. I will check out the docs and if not, the reference source for logic that indicates it’s valid and expected and not simply a fragile coincidence.

[zvirja]

@jcasale Feel free to use the NumericRangedRequestRelay or EnumRangedRequestRelay as a sample of such customization.

This API will be available since our next release that should happen in the nearby future.

Closing this one as no further action is required so far. Feel free to ask more questions if you have 😉