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

rjw57 / tawhiri / 41 / 1
18%
master: 1%

Build:
Build:
LAST BUILD BRANCH: add-etag
DEFAULT BRANCH: master
Ran 15 Nov 2014 11:25AM UTC
Files 9
Run time 5s
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

15 Nov 2014 11:20AM UTC coverage: 17.768%. Remained the same
41.1

push

travis-ci

rjw57
api: refactor as separate Flask Blueprint

Increase modularity by moving API into the tawhiri.api.v1 module and
re-expressing it as a Flask blueprint. This lets one specify the
location of the API as a single URL prefix when creating the Flask app.
It also allows single-API only applications as used, for example, in
testapi.py.

This PR makes no change to the logic of api.py. It merely moves the file
and allows central configuration of the URL prefix. See
http://flask.pocoo.org/docs/0.10/blueprints/ for more discussion of the
advantages of using Blueprints when considering application modularity.

The rationale for this modification is that it allows a) experimental or
"v2" APIs to be cleanly added and b) for APIs to share common
code/interfaces within the api module.

It is envisaged that some light re-factoring will lead to a module
within api which can be cleanly mocked to unit-test the web request
logic separately from the actual landing prediction code.

156 of 878 relevant lines covered (17.77%)

0.18 hits per line

Source Files on job 41.1
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 41
  • Travis Job 41.1
  • 06e7d67e on github
  • Prev Job for on api-refactor (#38.1)
  • Next Job for on api-refactor (#44.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