https://github.com/ajalt/timberkt

Easy Android logging with Kotlin and Timber
https://github.com/ajalt/timberkt

android kotlin kotlin-extensions logging

Last synced: 8 days ago
JSON representation

Easy Android logging with Kotlin and Timber

• Host: GitHub
• URL: https://github.com/ajalt/timberkt
• Owner: ajalt
• License: apache-2.0
• Created: 2016-06-29T03:42:05.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2019-05-09T15:49:44.000Z (over 5 years ago)
• Last Synced: 2024-10-22T15:17:18.864Z (17 days ago)
• Topics: android, kotlin, kotlin-extensions, logging
• Language: Kotlin
• Size: 163 KB
• Stars: 203
• Watchers: 5
• Forks: 12
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

• awesome-kotlin-android - timberkt - 基于Timber的日志库 🔥 (开源库 / 日志)

README

        
# Kotlin logging extensions for Timber

Jake Wharton's [Timber](https://github.com/JakeWharton/timber) library is great. It's a Java library with an API that works well for Java, but that isn't as idiomatic when used in Kotlin. 

This library builds on Timber with an API that's easier to use from Kotlin. Instead of using formatting parameters, you pass a lambda that is only evaluated if the message is logged.

## Usage

1. Configure any `Tree` instances in your Application's `onCreate`, the same way as with plain [Timber](https://github.com/JakeWharton/timber#usage).

2. Call the extension functions from anywhere in your code.

```kotlin

// Standard timber

Timber.d("%d %s", intVar + 3, stringFun())

// Kotlin extensions

Timber.d { "${intVar + 3} ${stringFun()}" }

// or

d { "${intVar + 3} ${stringFun()}" }

```

The same message and tags will be logged in all three cases. 

The Kotlin extensions have the advantage of being more convenient to write, and are also more performant in some circumstances. The passed block is only evaluated if the message is logged, and even if the message is logged to multiple trees, the block is only evaluated once. All extension methods are inlined, so there is no method count penalty to using this library.

Logging exception objects works the same way:

```kotlin

// Standard timber

Timber.e(exception, "%d exceptions", errorCount)

// Kotlin extensions

Timber.e(exception) { "$errorCount exceptions" }

// or

e(exception) { "$errorCount exceptions" }

```

## What about Timber's custom lint checks?

Timber comes with half a dozen lint checks that help you spot incorrect usage of the log calls. 

With the exception of long custom tags, none of the errors those checks look for are possible with this library. You can perform arbitrary code inside of the lambdas passed to the log extensions, and there's no risk of performance problems in your release code since the blocks won't be evaluated unless the messages are printed.

## Download

The Kotlin extensions for Timber are distributed with Maven Central, 

[JCenter](https://bintray.com/ajalt/maven/timberkt) and

[JitPack](https://jitpack.io/#ajalt/timberkt/1.5.1).

```groovy

implementation 'com.github.ajalt:timberkt:1.5.1'

```

## Documentation

[The documentation is hosted online here](https://jitpack.io/com/github/ajalt/timberkt/1.5.1/javadoc/timberkt/com.github.ajalt.timberkt/index.html).

## License

```

Copyright 2017-2018 AJ Alt

Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License.

You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

```