Releases: hoodiehq/hoodie-store-server
v3.0.0
<a name"3.0.0">
3.0.0 (2017-03-08)
Breaking Changes
The store instance which server.plugins.store.api.open(dbName) resolves to
has several breaking changes via pouchdb-hoodie-api@2.0.0
-
Before, change events (incl. add, update, remove) have only been triggered
when using the custom APIs like.add()or.update(). Now they get always
triggered, including for changes replicated into the database. -
the order of when the methods’ promises resolve and the events get triggered
cannot be guaranteed as we rely on PouchDB’s.changes(). We would love to
enforce promises to resolve after changes get emitted, but the required
complexity to do that is not worth it. -
We no longer map PouchDB’s ._id property to .id, instead we pass trough docs
from PouchDB 1:1. Also the timestamps are now all namespaced with
.hoodie(doc.createdAtbecomesdoc.hoodie.createdAt)
(7b2b04e5)