timberio / timber-elixir

75%

master: 42%

LAST BUILD ON BRANCH v3.0.0

branch: v3.0.0

CHANGE BRANCH

x

Reset

• v3.0.0
• 165-allow-phoenix-controller-whitelisting
• feature/install-task
• final-changes
• fix-dialyzer
• gc
• handle-new-hackney-messages
• hotfix/runtime-context
• json-formatting
• json-utility-methods
• master
• new-readme
• prepare-3.1
• prepare-3.x-line
• relax-hackney-versions
• remove-namespaces
• remove-unused-http-methods
• source-iod
• v2.5.2
• v3.1.0
• v3.1.1
• v3.1.2

Build # 748

Build Type

push

travis-ci

Committed by web-flow

Commit Message

3.0.0 Release (#314)

* Prepare 3.0 development

This commit is designed to prepare for 3.0+ development. In Timber
Elixir 3.0+, integration with other libraries will be done through
additional libraries in order to allow for better dependency management
and compilation guarantees. Timber Elixir 3.0+ will be required for
Elixir 1.7+ support.

All of the integration-specific code has been removed except for the
installer code. The installer code needs to be updated to appropriately
update the mix.exs files with the relevant integration libraries and
use the updated module names.

The weird dependency listing logic has been removed from mix.exs.

The README has also been fixed so that the markdown now renders
correctly.

This fixes the .formatter.exs file to look at the root `lib` folder.

This change adds Elixir 1.7.2 to the list of versions that Travis tests
for.

Addresses #298, fixes #209, fixes #162

* Change supported Elixir versions to ~> 1.4

The Timber library will now only support Elixir versions 1.4 and higher. To use
Timber with Elixir 1.3 (which support was removed for), please use a release
from the 2.x branch.

Supporting only Elixir 1.4+ will allow us to take advantage of the new Jason
library which is easier to maintain support for.

* Remove installer

This removes the installer. This decision was made because the
installer, while valuable, is difficult to maintain and has introduced a
number of bugs for end-users. Manual installation is now the preferred
method.

* Clean up and organize documentation

This organizes the documentation by providing groupings for the events and
contexts so they appear under headers in the ExDoc rendering. It also moves some
of the internal helper modules to not expose any documentation.

* Remove Timber.CurrentContext module

The Timber.CurrentContext module is deprecated and was slated for removal in the
3.x line. Its usecase is now handled by Timber.Loc... (continued)

Run Details

384 of 514 relevant lines covered (74.71%)

9.34 hits per line