Wrong patch when substituting an object for an array?

[maca]

> jsonpatch.compare({a: {}}, {a: [1]});
[{op: "add", path: "/a/0", value: 1}]

Shouldn't be the empty object replaced with the array? the value is no longer an object.

[{op: "replace", path: "/a", value: [1]}]

[jamesplease]

The same thing happens in reverse, too.

var x = jsonpatch.compare(['jack'], {});

// no good
x === [{
  op: "remove"
  path: "/0"
}];

and for an even bigger hint at what the issue is:

var x = jsonpatch.compare([], {});
x === [];

Deep down this library thinks that arrays and objects are the same thing! This likely stems from the fact that it only worries about the keys, which fails to differentiate arrays and objects in these edge cases.

[jamesplease]

@Starcounter-Jack @warpech are either of you around? I'll make up a PR sooner rather than later if you'll have time to review it.

[alshakero]

Will be fixed in #205