Releases: hoodiehq/hoodie-store-client
v8.3.0
v8.2.0
v8.1.4
v8.1.3
v8.1.2
v8.1.0
<a name"8.1.0">
8.1.0 (2017-03-09)
Features
- async
options.remote
via [[email protected]](https://github.com/hoodiehq (2b26cd23)
v8.0.1
v8.0.0
<a name"8.0.0">
8.0.0 (2017-03-04)
Features
Breaking Changes
-
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. hoodiehq/pouchdb-hoodie-api@1958c42 -
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.
-
separate methods like
require(pouchdb-hoodie-api/add)
can no longer be required directlyThe reason for that is that all the methods now also accept a
prefix
argument which by default is null. That way we don’t need to implement each method twice, once forstore.add
, and once forstore.withIdPrefix(test/).add
-
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.createdAt
becomesdoc.hoodie.createdAt
)
(852393e8)