An open source cybersecurity protocol for syncing decentralized graph data.
Significant changes from previous tags, check the changelog and documentation for migrations.
list.set(item)
returns the item's chain now, not the list chain.gun.get('mark').path('owner').put(gun.get('cat'))
.set
method: gun.get('users').set(gun.get('person/mark'))
.Amazon S3 driver compatibility/updates for breaking changes in v0.3.0
Fixes for Express.js compatibility
.wsp()
renamed from .attach()
..set()
deprecated because it did a bunch of random inconsistent things. Its useful behavior has now become implicit (see below) or can be done explicitly..not()
it was previously common to return
the chain inside of .not, beware that if you have code like gun.get(key).not(function(){ return this.put({}).key(key) }).val()
cause .val()
to be triggered twice (this is intentional, because it funnels two separate chains together) which previously didn't happen. To fix this, just don't return the chain..put()
and .path()
do implicit .init()
by default, turn on explicit behavior with Gun({init: true})
..get(soul, cb)
cb is called back with err, node
rather than err, graph
.opt.wire
renamed from opt.hooks
..val()
when called empty automatically cleanly logs for convenience purposes..init()
added.Gun.is.val
renamed from Gun.is.value
.Gun.is.rel
renamed from Gun.is.soul
.Gun.is.node.soul
renamed from Gun.is.soul.on
.Gun.union.ify
renamed from Gun.union.pseudo
.Gun.union.HAM
renamed from Gun.HAM
.Gun.HAM
is now the actual HAM function for conflict resolution.Gun._.state
renamed from Gun._.HAM
..on()
gets called when a key is later newly made while before it did not. #116.val()
should not ever get called with a relation alone (internals should resolve it), this is fixed. #132Fix Jesse's synchronous Trace bug