Avoid overflow when storing an int64 in an Integer

[joeljons]

In int64example.yaml the example value comes out as -81224344 in an Integer.

Maybe there is a better way of checking for int64 examples, but this seems to do the job at least. I'm happy to change if there is some obvious better way this should be done in. :)

[gracekarina]

Thanks!! @joeljons, I tried to push some changes but I have not permissions on your repo, so here is where I think it should be validated:

In the method getInteger()

line: 1196 : I added a boolean validation to make sure the number is an integer, it would return null if false and all integers will be validated as well

public Integer getInteger(String key, ObjectNode node, boolean required, String location, ParseResult result) {
        Integer value = null;
        JsonNode v = node.get(key);
        if (node == null || v == null) {
            if (required) {
                result.missing(location, key);
                result.invalid();
            }
        }
        else if(v.getNodeType().equals(JsonNodeType.NUMBER)) {
            if (v.isInt()) {
                value = v.intValue();
            }
        }
        else if(!v.isValueNode()) {
            result.invalidType(location, key, "integer", node);
        }
        return value;
    }

[gracekarina]

please check comment

[joeljons]

Your idea is much more elegant! :)
I will change my commit to implement it that way instead.

[gracekarina]

@joeljons thanks!