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

lazyengineering / faststatus / 112 / 1
90%
master: 90%

Build:
Build:
LAST BUILD BRANCH: simplify-construction
DEFAULT BRANCH: master
Ran 14 May 2017 12:37AM UTC
Files 7
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

14 May 2017 12:36AM UTC coverage: 90.105% (+0.1%) from 90.0%
112.1

push

travis-ci

jessecarl
Check for Stale data errors from the store

The RESTful server now checks for stale data errors from the store.
While this works, I think there are some key refactorings that need to
take place before we can consider this complete.

The rest package should not be importing the store package in order to
check for a stale data error. The error check functions that are used
across packages may need to be moved out of the store package and into
the root package.

If the error check functions used for the store are going to be moved
into the root package, the Store interface may be best placed there.
Additionally, the private `errorCode` function used in the rest package
may be updated to utilize the exported `StaleError` and `ZeroValueError`
functions to map to correct status codes (409 and 400 respectively).

428 of 475 relevant lines covered (90.11%)

449.29 hits per line

Source Files on job 112.1
  • Tree
  • List 0
  • Changed 7
  • Source Changed 2
  • Coverage Changed 7
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 112
  • Travis Job 112.1
  • ab47ad2d on github
  • Prev Job for on feature/distinct-errors (#111.1)
  • Next Job for on feature/distinct-errors (#114.2)
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