hoodiehq
/
hoodie-store-client
/
606
/
1
100%
master: 100%
master: 100%
|
Ran
|
Files
4
|
Run time
0s
|
Badge
Embed ▾
README BADGES
|
coverage: 100.0%. Remained the same
push
travis-ci
gr2mfeat: pouchdb-hoodie-api@2.0.0 BREAKING CHANGE: - 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. https://github.com/hoodiehq/pouchdb-hoodie-api/commit/1958c425b - 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 directly The 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 for `store.add`, and once for `store.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` becomes `doc.hoodie.createdAt`)
69 of 69 relevant lines covered (100.0%)
9.35 hits per line
