1
65%
master: 42%

Ran 24 Jan 2019 04:29PM UTC

Files 45

Run time 7min

Badge

Embed ▾

Committed 24 Jan 2019 04:21PM UTC coverage: 71.014% (-3.3%) from 74.286%

Job # 775.1

Build Type

Pull #326

travis-ci

Committed by

web-flow

Commit Message

Remove `event`, `event.custom`, and `context.custom` namespaces

Timber 2.0 no longer requires a strict schema, this means that events and contexts can be defined freely without the need to be nested under specific `event`, `event.custom`, or `context.custom` keys.

For example, this `http_response` event went from this:

```json
{
  "level": "info",
  "message": "Order abcd1234 placed",
  "event":
    "custom": {
      "order_placed": {
        "id": "abcd1234",
        "total": 100
      }
    }
  }
}
```

To this:

```json
{
  "level": "info",
  "message": "Order abcd1234 placed",
  "order_placed": {
    "id": "abcd1234",
    "total": 100
  }
}
```

Pull Request Pull Request #326: Remove `event`, `event.custom`, and `context.custom` namespaces

Run Details

343 of 483 relevant lines covered (71.01%)

7.52 hits per line

timberio / timber-elixir / 775 / 1
65%
master: 42%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 775.1

timberio / timber-elixir / 775 / 1 65% master: 42%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 775.1

timberio / timber-elixir / 775 / 1
65%
master: 42%

README BADGES
x