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

timberio / timber-elixir-phoenix / 37 / 1
95%
master: 94%

Build:
Build:
LAST BUILD BRANCH: v1.1.0
DEFAULT BRANCH: master
Ran 21 Jan 2019 08:37PM 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:22PM UTC coverage: 84.091% (-13.7%) from 97.826%
37.1

Pull #6

travis-ci

web-flow
Dont 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.
Pull Request #6: Dont use Timber structs when logging events

74 of 88 relevant lines covered (84.09%)

2.8 hits per line

Source Files on job 37.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 29
  • Travis Job 37.1
  • 2ac6c2d6 on github
  • Prev Job for on update-events (#29.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