LongNode(3) != IntNode(3)

The equals method for IntNode is implemented so that only IntNodes can be equal to other IntNodes, regardless of numeric value. This is obvious with just a glance at the source code.

I can do a PR to fix this, but just want to confirm that this isn’t so by design first.

[cowtowncoder]

I appreciate your reaching out first: makes sense.

This is by design, wrt default behavior. Users are encouraged to use

   public boolean equals(Comparator<JsonNode> comparator, JsonNode other);

method with suitable Comparator implementation for customizing equality logic to their liking.

The reason here is simply that attempting to support various kinds of coercion (DoubleNode, FloatNode too, presumably; BigIntegerNode, BigDecimalNode) leads to unmaintanable system. So although I agree in that it is not unreasonable to expect equality here, I am not interested in following this trail down the likely rat hole.

[cowtowncoder]

@grimsa Thank you for sharing this!

I wonder if there was some benefit to adding a configurable (Builder based) JsonNodeComparator on Jackson 2.11 or later? (possibly 3.0, to allow Java 8 method pointers)