mirror of
https://github.com/amark/gun.git
synced 2026-03-02 07:03:18 +00:00
2.4 KiB
2.4 KiB
CHANGELOG
0.3
Migration Guide! Migrate by changing .attach( to .wsp( on your server if you have one with gun. Change .set() (empty call) to `` (aka delete it), and change .set($DATA) (where you call set with something) to .path('I' + Date.now() + 'R' + Gun.text.random(5)).put($DATA). If you have NodeJS style callbacks in your .get (which documentation previously recommended that you shouldn't) they previous took err, graph and now they take err, node (which means now using callback style is fine to use). Inside of .not() no longer use return or this, instead (probably) use gun and no return. If you are a module developer, use opt.wire now instead of opt.hooks and message Mark since he needs to talk to you since the wire protocol has changed.
- 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 toreturnthe 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, noderather thanerr, graph.- Options
opt.wirerenamed fromopt.hooks. .val()when called empty automatically cleanly logs for convenience purposes..init()added.Gun.is.valrenamed fromGun.is.value.Gun.is.relrenamed fromGun.is.soul.Gun.is.node.soulrenamed fromGun.is.soul.on.Gun.union.ifyrenamed fromGun.union.pseudo.Gun.union.HAMrenamed fromGun.HAM.Gun.HAMis now the actual HAM function for conflict resolution.Gun._.staterenamed 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