1.0 <> 1

If I compare the following 2 fragments:

expected:

```
{
"value" : 1.0
}
```

test data:

```
{
"value" : 1
}
```

zjsonpatch considers this different and generates a As far as I am aware, in JavaScript/JSON there is no distinction between integers and floats/doubles: they are all considered 'numbers'.

zjsonpatch should not generate a "replace" patch node for this.

The issue gives the expected and test JSON values but names no source file or test. Start by locating the JSON comparison and numeric equality entry points, then inspect existing tests for number comparisons. Done means equivalent integer and floating-point JSON numbers no longer produce a replace patch, while genuinely different numbers still do.

Written by the indexing model from the issue text.