Oh, if you try to run the above, dagger will say it can’t provide the

addFunc

as a dep for

plus3

, but if you delete that, and only have

provideAddFunc

and

val addFunc

on the component, everything works fine, and can be injected etc

Did you miss the

@Inject

on the

fun providePlus3

?

No, I’m accessing the object on the component directly via

private val plus3 : (Int) -> Int by lazy { component.plus3 }

wow even the basic import of samples doesn’t work in AS anymore

there’s something totally insane about providing SO much sample code, then the import process is borked out of what looks like sheer laziness: gradle is reporting that it cannot find target that has the string android-O, probably because it’s now oreo. But the stupidest part is the build.gradle file cannot be opened. Because it cannot interpret the broken build.gradle file.

looks like the problem is samples from the grouping called o preview, the PiP sample from the oreo group imports and runs immediately..

file a bug

Does anyone knows an alternative to always having to Clean and Rebuild project before running the app in Android Studio 2.3.3?

any time you have to run 'clean' is a bug in something

I heard about "Kotlin for Android Developers"

How can I extract just numbers from a string like "USA (+1)"

You can use filter on the String.

val numbers = myString.filter { it.isDigit() }

Can anyone help me with this Rxjava2 and Kotlin code?

@alex.krupa commented on @vicky7230’s file : There is no ternary operator in Kotlin

@alex.krupa commented on @vicky7230’s file : The closest thing is just a regular

if else

, i.e.

if (boolean) null else "Invalid Email"

Please help me to convert this into Kotlin

your generic classes need to be public for that to work

shift + command + a

followed by

convert to kotlin

works wonders on existing java classes

Not able to solve this error

@yuriy.stetsyk commented on @vicky7230’s file : Pass Type to BaseViewModel, as it is generic type. BaseViewModel<N>, use any class that suits your need in place of N

I think it’s always best to pass the context in via it’s methods, than caching the context in the object

BaseViewModel is expecting a type

Yeah, for the application context I create a lateinit var in the companion object of the Application subclass

@ech0s7r Well your Repository should be normal class that has constructor with Context and is provided via DI that makes it Singleton, you should not make it Singleton with object

¯\_(ツ)_/¯

I think some http clients (like koush/Ion) need a context to run in... maybe he needsnetwork requests in his repo...

Hi, I'm putting together a group of libraries for Kotlin/Android and I expect the API to change based on feedback from future users. I'm wondering which approach I should take to avoid migrations pains if the API changes. I know the kotlinx.coroutines approach which is putting everything in a subpackage named "experimental", and provide migrations with

@Deprecated

along with

ReplaceWith

when the API stabilizes, and I know of the more traditional Android Architecture Components approach which is just using alpha and beta keywords. Could you help me decide by telling and possibly weighing the pros and cons you find in these approaches or others you know? Thanks for your help!

@ech0s7r Just create this repository object, pass context to constructor, then cache it in your application class (if you really need singleton). Then use this instance to create instances of other classes that depend on it. It's called dependency injection, architecture/design technique/principal

Not to go too far into a tangent on this, but does anyone have recommended resources for learning about DI? I am late to the party on this and haven't really found anything that helpful yet.