hoodiehq / hoodie-server / 1695

100%

next: 82%

push

travis-ci

chore(package): @hoodie/store-server 3.0.0

BREAKING CHANGE:

The store instance which `server.plugins.store.api.open(dbName)` resolves to
has several breaking changes via [pouchdb-hoodie-api@2.0.0](https://github.com/hoodiehq/pouchdb-hoodie-api/releases/tag/v2.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.createdAt` becomes `doc.hoodie.createdAt`)

Unless you use the `server.plugins.store.api.open(name)` API you are not affected by any of this.

42 of 42 branches covered (100.0%)

145 of 145 relevant lines covered (100.0%)

3.08 hits per line