Type mismatch in comparison

Is it possible to add an enum for type mismatch as well?

In one of my use case, the value at a particular JSON patch was same but one was of type string and other was of type long and I wasn't able to figure out the reason for failure.

Start by locating the Java comparison logic and any existing error or enum definitions in the JSON Patch implementation. Reproduce a patch where equal-looking values differ as string and long, then verify that the resulting failure clearly identifies a type mismatch and is covered by a regression test.

Written by the indexing model from the issue text.