IntegerSchema instead NumberSchema at 2.4.0/2.4.1

[alexei-zaycev]

HI!

final ObjectMapper mapper = new ObjectMapper();
final JsonSchemaGenerator generator = new JsonSchemaGenerator(mapper);
final JsonSchema schema = generator.generateSchema(Double.class);
mapper.writeValue(System.out, schema);

at version 2.4.0/2.4.1 result:

{"type":"integer"}

at version 2.3.4 result:

{"type":"number"}

[cowtowncoder]

Interesting. Right, double not an int (ditto for Double vs Integer)

[alexei-zaycev]

in 2.4.3 the problem persists

pojo:

public class T {
    public final int x;
    public final double y;
}

schema generator:

final ObjectMapper mapper = new ObjectMapper();
final JsonSchemaGenerator generator = new JsonSchemaGenerator(mapper);
final JsonSchema schema = generator.generateSchema(T.class);
mapper.writeValue(System.out, schema);

result:

{
    "type":"object",
    "properties": {
        "x":{"type":"integer"},
        "y":{"type":"integer"}
    }
}

although it should be:

{
    "type":"object",
    "properties": {
        "x":{"type":"integer"},
        "y":{"type":"number"}
    }
}

[cowtowncoder]

Actual fix is in jackson-databind, but with 2.4.4 release it should be resolved. There is one residual problem with BigDecimal/BigInteger, which will be fully fixed in 2.5.0.