Summary
object-observer
provides a deep observation of a changes performed on an object/array graph.
Main aspects and features:
-
implemented via native Proxy (revokable)
-
observation is 'deep', yielding changes from a sub-graphs too
-
nested objects of the observable graph are observables too
-
changes delivered in a synchronous way by default, asynchronous delivery (experimental) is optionally available as per Observable
configuration; more details here
-
observed path may optionally be filtered as per observer
configuration; more details here
-
original objects are cloned while turned into Observable
s
-
array specifics:
- generic object-like mutations supported
- intrinsic
Array
mutation methods supported: pop
, push
, shift
, unshift
, reverse
, sort
, fill
, splice
, copyWithin
- massive mutations delivered in a single callback, usually having an array of an atomic changes
-
typed array specifics:
- generic object-like mutations supported
- intrinsic
TypedArray
mutation methods supported: reverse
, sort
, fill
, set
, copyWithin
- massive mutations delivered in a single callback, usually having an array of an atomic changes
-
intrinsic mutation methods of Map
, WeakMap
, Set
, WeakSet
(set
, delete
) etc are not observed (see this issue for more details)
-
following host objects (and their extensions) are skipped from cloning / turning into observables: Date
, Blob
, Error
Support matrix: 61+ | 60+ | 16+ | 8.10.0+
Performance report can be found here
Last versions (full changelog is here)
-
4.0.4
- Issue no. 65 - fixed a broken keys order of the cloned observable
- added perf tests
-
4.0.2
- implemented Issue no. 61 - removed the CJS fashioned NodeJS flavor distribution
-
3.2.0
- implemented Issue no. 45 - implemented async flavor of changes delivery on per Observable configuration basis; default behavior remained the same - synchronous
- implemented Issue no. 51 - batch delivery of
Object.assign
changes is enabled via the async opt-in, see issue #45 above
For a preview/playground you are welcome to:
Loading
object-observer
provided as an ES6 module.
import { Observable } from 'dist/object-observer.min.js';
API
Library implements Observable
API as it is defined here.
Examples
Objects
const
order = { type: 'book', pid: 102, ammount: 5, remark: 'remove me' },
observableOrder = Observable.from(order);
observableOrder.observe(changes => {
changes.forEach(change => {
console.log(change);
});
});
observableOrder.ammount = 7;
observableOrder.address = {
street: 'Str 75',
apt: 29
};
observableOrder.address.apt = 30;
delete observableOrder.remark;
Object.assign(observableOrder, { amount: 1, remark: 'less is more' }, { async: true });
Arrays
let a = [ 1, 2, 3, 4, 5 ],
observableA = Observable.from(a);
observableA.observe(changes => {
changes.forEach(change => {
console.log(change);
});
});
observableA.pop();
observableA.push('a', 'b');
observableA.shift();
observableA.unshift('x', 'y');
observableA.reverse();
observableA.sort();
observableA.fill(0, 0, 1);
observableA.splice(0, 1, 'x', 'y');
let customer = { orders: [ ... ] },
oCustomer = Observable.from(customer);
oCustomer.orders.sort();
oCustomer.orders.reverse();
Arrays notes: Some of array operations are effectively moving/reindexing the whole array (shift, unshift, splice, reverse, sort).
In cases of massive changes touching presumably the whole array I took a pessimistic approach with a special non-detailed events: 'reverse' for reverse
, 'shuffle' for sort
. The rest of these methods I'm handling in an optimistic way delivering the changes that are directly related to the method invocation, while leaving out the implicit outcomes like reindexing of the rest of the Array.
Observation options
object-observer
allows to filter the events delivered to each callback/listener by an optional configuration object passed to the observe
API.
In the examples below assume that callback = changes => {...}
.
let user = {
firstName: 'Aya',
lastName: 'Guller',
address: {
city: 'of mountaineers',
street: 'of the top ridges',
block: 123,
extra: {
data: {}
}
}
},
oUser = Observable.from(user);
oUser.observe(callback, {path: 'firstName'});
oUser.observe(callback, {path: 'address.city'});
oUser.observe(callback, {pathsOf: 'address'});
oUser.observe(callback, {pathsFrom: 'address'});