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

timberio / timber-elixir-phoenix / 34 / 1
94%
master: 94%

Build:
DEFAULT BRANCH: master
Ran 21 Jan 2019 08:22PM 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

21 Jan 2019 08:19PM UTC coverage: 84.091% (-13.7%) from 97.826%
34.1

push

travis-ci

binarylogic
Don't use Timber structs when logging events

Timber 2.0 no longer requires a strict schema, this allows events to be logged freely without the concern that events will be rejected if they do not
pass validation. As a result, Timber integration no longer need to use defined event structs, they can simply log the event just as any Timber client
would log a custom event. This gives integrations the freedome to name and define events in any structure they please.

Concrete changes:

* Stopped using `Timber.Events.*` in favor of simple maps
* Updated event names to use the verb past-tense, which follows the recommended naming scheme from Timber
* Moved all `metadata.*` attribute to the root of the event payload.

74 of 88 relevant lines covered (84.09%)

2.8 hits per line

Source Files on job 34.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 26
  • Travis Job 34.1
  • 68b80a4d on github
  • Prev Job for on master (#29.1)
  • Next Job for on master (#36.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