Incorrect results of RangeAttribute

[martinmikulka]

Hello, I've encountered a strange behaviour of the RangeAttribute when attempting to set a negative value. Values between -0.5 and 0 are evaluated as valid.

Model:

    public class MyModel
    {
        [Range(0, 1)]
        public double Test { get; set; }
    }

Controller:

    [HttpPost]
    public IActionResult Test(MyModel model)
    {
        var tests = new double[] { -1, -0.6, -0.51, -0.5, -0.49, -0.4, -0.1, 0 };
        foreach (var test in tests)
        {
            model.Test = test;
            ModelState.Clear();
            TryValidateModel(model);
            Console.WriteLine($"Value: {model.Test}, Result: {ModelState.IsValid}");
        }

        return Ok();
    }

Results:
Value: -1, Result: False
Value: -0,6, Result: False
Value: -0,51, Result: False
Value: -0,5, Result: True
Value: -0,49, Result: True
Value: -0,4, Result: True
Value: -0,1, Result: True
Value: 0, Result: True

dotnet --info
SADA .NET SDK:
 Version:   6.0.407
 Commit:    d8659ea151

Runtime:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.407\

global.json file:
  Not found

Host:
  Version:      6.0.15
  Architecture: x64
  Commit:       5edef4b20b

[martinmikulka]

It seems the min/max value types provided in the attribute need to match with the data type of the model.

    public class MyModel
    {
        [Range(0.0, 1.0)]
        public double Test { get; set; }
    }

Results:
Value: -1, Result: False
Value: -0,6, Result: False
Value: -0,51, Result: False
Value: -0,5, Result: False
Value: -0,49, Result: False
Value: -0,4, Result: False
Value: -0,1, Result: False
Value: 0, Result: True

[javiercn]

@martinmikulka thanks for contacting us.

Yes, I believe the data types must match as per the implementation https://github.com/dotnet/runtime/blob/main/src/libraries/System.ComponentModel.Annotations/src/System/ComponentModel/DataAnnotations/RangeAttribute.cs which means the double value gets implicitly casted to an integer

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.