Inspect code for bugs that are not covered by tests

[warpech]

After #39

The code in https://github.com/Palindrom/JSONPatcherProxy/blob/c461b492a4fa2e2869ba99cbe0329db3846e93cd/src/jsonpatcherproxy.js contains several TODO statements that mark places for functionality that is not tested.

Also check why running the test suite results in so many console loigs. Is this by design, or are some of these console logs actually pointing out a problem:

λ npm run test

> [email protected] test W:\repo\JSONPatcherProxy
> jasmine DUPLEX=proxy JASMINE_CONFIG_PATH=test/jasmine.json

Started
...........You're accessing an object that is detached from the observedObject tree, see https://github.com/Palindrom/JSONPatcherProxy#detached-objects
..JSONPatcherProxy noticed a non-integer prop was set for an array. This will not emit a patch
JSONPatcherProxy noticed a non-integer prop was set for an array. This will not emit a patch
.....JSONPatcherProxy noticed a non-integer prop was set for an array. This will not emit a patch
JSONPatcherProxy noticed a non-integer prop was set for an array. This will not emit a patch
.........................You're accessing an object that is detached from the observedObject tree, see https://github.com/Palindrom/JSONPatcherProxy#detached-objects
You're accessing an object that is detached from the observedObject tree, see https://github.com/Palindrom/JSONPatcherProxy#detached-objects
.......

[warpech]

Regarding the TODO in the line

JSONPatcherProxy/src/jsonpatcherproxy.js

Line 280 in c461b49

this._isProxifyingTreeNow = true; //TODO probably not needed, when I comment this out, all tests pass

, do not miss the comment in #39 (comment)