Starting with Kotlin Coroutines version
ConflatedBroadcastChannel were marked as
ObsoleteCoroutinesApi and developers should now use
Kotlin documentation even gives a handy guide on how to migrate from these channels to respective Flow APIs:
I’ve come up with one idea and while I don’t think backing fields are so evil that they need to be…
Some of you may have recently started using Kotlin Flow, the new framework by JetBrains to handle observable streams.
As you probably already know from many articles on the internet, in order to collect a flow, you have two main options. You can either use
.collect() , or
A very short tutorial on how to use Dagger.Hilt if you don’t have time to read through the docs.
Add gradle dependencies:
// project's build.gradle
// your other dependencies// Dagger Hilt
// other dependencies
Extension functions are without doubt one of Kotlin’s most loved features. Most articles on the internet and even many libraries use them, however, only for simple utility methods, that might be useful across whole project.
In fact, you’ll even find articles like this one that even warns you about misusing…
In the discussion under my previous article on using Dagger 2 in multi-module Android applications, some questions arose about dealing with multiple build targets. That is, what if I want to build the same app in two versions, where most of the code is shared, but the other app has…
It seems it’s still not easy for many Android developers to figure out how to use Dagger2 for dependency injection in a multi-module application.
Sure, if you’re keeping all your activities in the main module, then you don’t have a problem. That’s not the most natural way of separating code…