maximum/minimum use decimal which do not parse certain many double "number" strings about json-everything HOT 3 CLOSED

This was an intentional design decision.

While IEEE floating point numbers support a greater range, decimal supports greater precision, which often is needed more, for instance in financial applications.

JSON itself supports arbitrary-precision numbers, but it also does have a note that computers have limitations in numeric representation.

JSON Schema has no such requirements, instead deferring to JSON.

I've even marked the appropriate test as skipped in the test suite as listed on Bowtie (find my implementation and click "Details").

from json-everything.

@marcschier I have a workaround for you: copy the existing keywords that use decimal (i.e. MinimumKeyword, etc.) and modify them to use double. Then you just need to register them, and they should work just fine.

Here's a quick test I ran to make sure it works:

SchemaKeywordRegistry.Register<MinimumDoubleKeyword>(TestSerializerContext.Default);

var text = $$"""
    {
        "type": "number",
        "minimum": {{float.MaxValue}}
    }       
    """;
var schema = JsonSerializer.Deserialize(text, TestSerializerContext.Default.JsonSchema);
JsonNode instance = (double)float.MaxValue * 5;
var result = schema.Evaluate(instance, new EvaluationOptions { OutputFormat = OutputFormat.Hierarchical });

result.AssertValid();

from json-everything.

It is also not possible to generate the Json schemas:

var schema = new JsonSchemaBuilder()
                    .Type(SchemaValueType.Number)
                    .Format("float")
                    .Minimum(Convert.ToDecimal(float.MinValue))
                    .Maximum(Convert.ToDecimal(float.MaxValue))
                    .Const(0f)
                    .Build(),

Results into runtime error message: System.OverflowException : Value was either too large or too small for a Decimal.

from json-everything.