ES6 proxy powered JSON Object observer that emits JSON patches when changes occur to your object tree.
With JSONPatcherProxy, you don't need polling or dirty checking. Any changes to the object are synchronously emitted.
JSON-Patch (RFC6902) is a standard format that allows you to update a JSON document by sending the changes rather than the whole document. JSONPatcherProxy plays well with the HTTP PATCH verb (method) and REST style programming.
Mark Nottingham has a nice blog about it.
- 1.30 KB minified and gzipped (3.25 KB minified)
- Allows you to watch an object and record all patches for later usage.
- Allows you to watch an object and handle individual patches synchronously through a callback.
- Tested in Edge, Firefox, Chrome, Safari and Node.js.
Install the current version (and save it as a dependency):
$ npm install jsonpatcherproxy --saveLoad the bundled distribution script:
<script src="dist/jsonpatcherproxy.min.js"></script>In browsers that support ECMAScript modules, the below code uses this library as a module:
<script type="module">
import { JSONPatcherProxy } from 'jsonpatcherproxy/src/jsonpatcherproxy.mjs';
</script>You can use rawgit.com as a CDN.
import { JSONPatcherProxy } from 'jsonpatcherproxy';var myObj = { firstName:"Joachim", lastName:"Wester", contactDetails: { phoneNumbers: [ { number:"555-123" }] } };
var jsonPatcherProxy = new JSONPatcherProxy( myObj );
var observedObject = jsonPatcherProxy.observe(true);
observedObject.firstName = "Albert";
observedObject.contactDetails.phoneNumbers[0].number = "123";
observedObject.contactDetails.phoneNumbers.push({number:"456"});
var patches = jsonPatcherProxy.generate();
// patches == [
// { op:"replace", path="/firstName", value:"Albert"},
// { op:"replace", path="/contactDetails/phoneNumbers/0/number", value:"123"},
// { op:"add", path="/contactDetails/phoneNumbers/1", value:{number:"456"}}];var myObj = { firstName:"Joachim", lastName:"Wester", contactDetails: { phoneNumbers: [ { number:"555-123" }] } };
var jsonPatcherProxy = new JSONPatcherProxy( myObj );
var observedObject = jsonPatcherProxy.observe(true, function(patch) {
// patch == { op:"replace", path="/firstName", value:"Albert"}
});
observedObject.firstName = "Albert";constructor: JSONPatcherProxy( root Object, [showDetachedWarning Boolean = true] ): JSONPatcherProxy
Creates an instance of JSONPatcherProxy around your object of interest root, for later observe, unobserve, pause, resume calls.
Returns JSONPatcherProxy.
root: The object tree you want to observe
showDetachedWarning: Modifying a child object that is detached from the parent tree is not recommended, because the object will continue to be a Proxy. That's why JSONPatcherProxy warns when a detached proxy is accessed. You can set this to false to disable those warnings.
Sets up a deep proxy observer on root that listens for changes in the tree. When changes are detected, the optional callback is called with the generated single patch as the parameter.
record: if set to false, all changes are will be pass through the callback and no history will be kept. If set to true patches history will be kept until you call generate, this will return several patches and deletes them from history.
Returns a Proxy mirror of your object.
- Note 1: you must either set
recordtotrueor pass a callback. - Note 2: you have to use the return value of this function as your object of interest. Changes to the original object will go unnoticed.
- Note 3: please make sure to call
JSONPatcherProxy#generateoften if you choose to record. Because the patches will accumulate if you don't.
🚨 Generated patches are not immutable. See "Limitations" below.
It returns the changes of your object since the last time it's called. You have to be recording (by setting record to true) when calling JSONPatcherProxy#observe.
If there are no pending changes in root, returns an empty array (length 0).
🚨 Generated patches are not immutable. See "Limitations" below.
Disables patches emitting (to both callback and patches array). However, the object will be updated if you change it.
Enables patches emitting (to both callback and patches array). Starting from the moment you call it.
De-proxifies (revokes) all the proxies that were created either in #observe call or by adding sub-objects to the tree in runtime.
Turns the proxified object into a forward-proxy object; doesn't emit any patches anymore, like a normal object.
As undefined type does not exist in JSON, it's also not a valid value of JSON Patch operation. Therefore JSONPatcherProxy will not generate JSON Patches that sets anything to undefined.
Whenever a value is set to undefined in JS, JSONPatcherProxy method generate and compare will treat it similarly to how JavaScript method JSON.stringify (MDN) treats them:
If
undefined(...) is encountered during conversion it is either omitted (when it is found in an object) or censored tonull(when it is found in an array).
See the ECMAScript spec for details.
-
It mutates your original object: During proxification, JSONPatcherProxy mutates the object you pass to it. Because it doesn't deep-clone for better performance. If you want your original object to remain untouched, please deep-clone before you pass it to the constructor.
-
It does not support multi-level proxification: During proxification, it recursively traverses the object and sets each property to its new proxified version. This means you can't proxify an already proxified object because the original proxy will record proxification as a series of changes. And the emitted patches are unpredictable. Also, when you change a property from either one of the proxies, both of the proxies will emit patches in an undefined manner.
-
Generated patches are not immutable. The patches generated by JSONPatcherProxy contain reference to the profixied object as the patch
value. You should either serialize the patch to JSON immediately or deep clone the value it if you want to process it later. If you don't do that, you run the risk that reading the patch will contain changes added after the patch was generated. -
JSONPatcherProxy might not generate patches for changes of integers above
Number.MAX_SAFE_INTEGER, or any other changes beyond the precision of JavaScript double-precision floating-point. To reduce patch generation noise, JSONPatcherProxy compares if the new value is the same (===) as the previous one. If so, then no patch is generated. Therefore, a change fromNumber.MAX_SAFE_INTEGER + 1toNumber.MAX_SAFE_INTEGER + 2, or from0.02to0.020000000000000001will not be effectively observed.
Go to /test
Run:
npm test
When you run npm run bench, few things happen:
- Five benchmark specs defined in
proxyBenchmark.jsare executed. This might take a minute. - The results are appended to the
benchmark.tsvfile, including the following information for each spec:- current Git commit SHA
- number of operations per second
- name of the spec
- At the end, in your console you will see the detailed information about the current benchmark, and the comparison of all data found in
benchmark.tsvrelatively to the first results for each given spec name, e.g.:
Observe and generate, small object (JSONPatcherProxy)
ec7b9bf: 136720 Ops/sec
92da649: 136351 Ops/sec (0.3% worse)
Observe and generate (JSONPatcherProxy)
ec7b9bf: 2762 Ops/sec
92da649: 2793 Ops/sec (1.1% better)
Primitive mutation (JSONPatcherProxy)
ec7b9bf: 781852 Ops/sec
92da649: 781270 Ops/sec (0.1% worse)
Complex mutation (JSONPatcherProxy)
ec7b9bf: 11808 Ops/sec
92da649: 10692 Ops/sec (9.5% worse)
Serialization (JSONPatcherProxy)
ec7b9bf: 1719 Ops/sec
92da649: 1719 Ops/sec (no difference)- Fork it.
- Clone it locally.
- Run
npm install. - Run
npm testto make sure tests pass before touching the code. - Modify, test again, push, and send a PR!
Version bumping is automated. Just use npm version command and all files will be updated with the new version.
MIT