Releases: amark/gun
Releases · amark/gun
out of date, use npm or cdn for latest
0.2019.413 improve CSS, Meta Editor, & CDN.
0.9.999998: Merge pull request #689 from 71/patch-1
Make node-webcrypto-ossl an optional dependency.
0.7.0
0.6.3
v0.3.4
- Breaking Change!
list.set(item)
returns the item's chain now, not the list chain. - Client and Server GUN servers are now more up to spec, trimmed excess HTTP/REST header data.
- Gun.is.lex added.
v0.3.3
- Native node links for shorthand graph structures
You can now easily link nodes by passing it's gun reference,gun.get('mark').path('owner').put(gun.get('cat'))
- Core integration for lists/tables/collections
Gun now supports a shorthand for lists using the.set
method:gun.get('users').set(gun.get('person/mark'))
.
v0.3.2
Amazon S3 driver compatibility/updates for breaking changes in v0.3.0
v0.3.1
Fixes for Express.js compatibility
v0.3.0
- Server side default
.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 toreturn
the chain inside of .not, beware that if you have code likegun.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 withGun({init: true})
..get(soul, cb)
cb is called back witherr, node
rather thanerr, graph
.- Options
opt.wire
renamed fromopt.hooks
. .val()
when called empty automatically cleanly logs for convenience purposes..init()
added.Gun.is.val
renamed fromGun.is.value
.Gun.is.rel
renamed fromGun.is.soul
.Gun.is.node.soul
renamed fromGun.is.soul.on
.Gun.union.ify
renamed fromGun.union.pseudo
.Gun.union.HAM
renamed fromGun.HAM
.Gun.HAM
is now the actual HAM function for conflict resolution.Gun._.state
renamed fromGun._.HAM
.- Maximum Callstack Exceeded is less problematic now, unless you intentionally choke the thread. #95
- Putting a regex or Date or NaN is actually detected and causes an error now while before it was silent. #122 #123
.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. #132
v0.2.5
Fix Jesse's synchronous Trace bug