• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

hoodiehq / hoodie-store-server / 466 / 1
87%
master: 87%

Build:
DEFAULT BRANCH: master
Ran 08 Mar 2017 04:46AM UTC
Files 2
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Mar 2017 04:45AM UTC coverage: 86.765% (-4.5%) from 91.304%
466.1

push

travis-ci

gr2m
chore(package): @hoodie/store-server-api 2.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`)

17 of 22 branches covered (77.27%)

42 of 46 relevant lines covered (91.3%)

2.04 hits per line

Source Files on job 466.1
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 466
  • Travis Job 466.1
  • 7b2b04e5 on github
  • Prev Job for on master (#461.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc