And all we have to do is use it! So let’s look at how to do this in Android. Luckily, there is already a perfect solution out of the box in the form of. So it looks like all the options are not quite what we need… But that would mean we have to inject it in every class we need logging in, which is far from convenient and seems like an overkill. But while such library could alleviate all of our problems, it would mean that we had to add the dependency to it in every module of our app, including our domain, and we would want to avoid that, especially for something as trivial as logging.Ĥ) Finally, probably the cleanest way would be to set up a logging interface in domain, implement it somewhere else (for example in the app module), and provide it via dependency injection.
Moreover, we might probably want to organize logging in one place, rather that having it scattered throughout the app.ģ) The next thing we might try is using one of the third-party libraries, most notably Timber. But while we can use this method from anywhere in the app, it doesn’t provide different log levels. With this we can very easily print logs into logcat, and the messages will appear under the tag “System.out”. The problem here though is that it is a part of an Android library, so we can’t use it in our domain module (and other pure Kotlin modules we might have).Ģ) We might also look at Kotlin’s println function. It has a concise syntax and support for different log levels (error, debug, info, etc.), which is a good thing. It is a standard Android way of writing logs, that can be then viewed in logcat. Let’s see what options we have:ġ) The first thing that comes to mind is, of course, the Android Log class. So, we need a logging mechanism that can be accessed in every module (including domain). And as this module doesn’t really need to know anything about Android, we made it a pure Kotlin module (i.e. Among our modules we have a domain module that contains business logic of the app - domain entities and interactors.
0 kommentar(er)
