https://kotlinlang.org logo
Join the conversationJoin Slack
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by Linen
koin-dev
  • m

    Mihai Voicescu

    11/12/2021, 5:45 PM
    Correct me if I am wrong, Koin in JS seem to be using
    ::class.getFullName()
    as the qualifier. This seems to have a major drawback: if 2 classes are named the same they will count as the same one, even though they are different Why not use
    ::class.js
    as the qualifier? This grants access to the actual JS implementation so even if 2 classes are named the same they will count as different. If you really want the Map.Key of the instances to be String you can also use
    ::class.js.name
    . This will provide the actual name of the class which should be unique given a module at least. Maybe even use the
    typeOf<T>()
    as the key? This should also solve template collision.
    a
    • 2
    • 3
  • r

    russhwolf

    11/16/2021, 6:15 PM
    Any chance of getting https://github.com/InsertKoinIO/koin/pull/1192 into a release at some point? I believe it's the last barrier to getting KaMPKit working with M1 targets.
    a
    m
    d
    • 4
    • 4
  • s

    Shalom Halbert

    11/27/2021, 1:28 PM
    Spent a bunch of time trying to setup Koin for instrumented tests. Started by trying to use
    loadModules
    and
    unloadModules
    , which worked…until I found out it that the module didn’t load before tests started. That yielded test failures that were difficult to debug. The solution, that doesn’t require test code in production code, was to: 1. Create a new class that extends the production
    Application
    class, let’s call the child
    InstrumentedTestApplication
    2. In
    InstrumentedTestApplication
    , override the list of modules provided in `startKoin`’s
    modules
    declaration to include a
    testModule
    3. Create a new class that extends
    AndroidJunitRunner
    , let’s call it
    InstrumentedTestJunitRunner
    that will instantiate
    InstrumentedTestApplication
    4. Point
    testInstrumentationRunner
    in the app-level build.gradle to
    InstrumentedTestJunitRunner
    Is this something that is in the Koin documentation, and I missed it? If not, is there interest in having it added?
    a
    • 2
    • 6
  • m

    Marcello Galhardo

    12/14/2021, 11:01 AM
    Question: I see we can load properties from files or by manually adding it to Koin by using the DSL. However, from the DSL we can use the type system (it has a generic parameter) but from the file system it is always considered a String. However, when you load the properties you may run into runtime exceptions if you request a type from the file system property. (Please, see the print screen for the comparison). Is there a reason for this design? It feels really misleading and can cause runtime exceptions if you call the wrong combination. In my humble opinion, we should have 3 possible designs here: 1. All are properties typed (primitives). 2. All are untyped (Strings). 3. We separate the concepts of file system properties and normal properties - and each one of these have a different API (one typed and one untyped). What are your opinions?
    a
    • 2
    • 6
  • a

    arnaud.giuliani

    01/07/2022, 4:45 PM
    Koin 3.2.0 in preparation for first betas
    :kotlin-intensifies: 1
    j
    • 2
    • 2
  • s

    sendoav

    01/19/2022, 10:06 PM
    Hi All! I'm injecting a "presenter" object into my compose views and every time a recomposition happens the presenter is recreated, how could I preserve the first created object? I have read that viewModel{} should work that way but I'm using KMM, so I cannot relay on android VM
    r
    m
    d
    • 4
    • 8
  • v

    Vivek Modi

    01/22/2022, 4:50 PM
    What is d/w by
    inject()
    and
    viewModel()
    ? I used both in when injecting in viewmodel and both works fine. I didn't figure out what the d/w in both. Which one need to use for viewModel. Any suggestions? Thanks
    t
    • 2
    • 8
  • a

    arnaud.giuliani

    02/09/2022, 3:17 PM
    I believe the same: • https://insert-koin.io/docs/3.2/reference/koin-core/dsl#withoptions---dsl-options • https://insert-koin.io/docs/3.2/reference/koin-core/dsl-update/ • https://insert-koin.io/docs/3.2/reference/koin-android/dsl-update/
    m
    • 2
    • 1
  • a

    arnaud.giuliani

    02/09/2022, 3:18 PM
    this allow to have something coherent on both DSL 👍
    m
    • 2
    • 4
  • a

    arnaud.giuliani

    02/09/2022, 3:19 PM
    Checking the
    includes
    contribution. Seeing some perf impact, trying to see if I can optimise it a bit before releasing first 3.2.0-beta-1
    m
    • 2
    • 5
  • p

    Pedro Francisco de Sousa Neto

    02/15/2022, 7:58 PM
    Hello everyone! I’ve created my first PR contributing with Koin. It’s very simple, fixing one typo in new doc rsrs. Issue -> https://github.com/InsertKoinIO/koin/issues/1294 Pull Request -> https://github.com/InsertKoinIO/koin/pull/1293
    a
    m
    • 3
    • 2
  • m

    Marcello Galhardo

    02/16/2022, 5:59 PM
    Hey folks, do you think it makes sense to add Kotlin’s Binary Compatibility Validator to Koin to try to reduce breaking changes? For that, we would need to add the library + include the checks to the CI to ensure PRs aren’t added by mistake. 🤔
    a
    • 2
    • 1
  • r

    Ruben Quadros

    03/25/2022, 5:19 PM
    Hi guys, this is regarding this PR. Want your suggestions. More info in the thread
    a
    • 2
    • 8
  • v

    Viktor Orlyk

    04/21/2022, 12:08 PM
    Hi, guys. I am relatively new to koin and ktor but this looks like there is some mismatching between ktor 2.0 and koin 3.2.0-beta-1. Maybe there is some more new version of docs instead of https://insert-koin.io/docs/reference/koin-ktor/ktor/ ? while trying to create extension fn run into next error.
    implementation("io.insert-koin:koin-ktor:$koin_version")
        implementation("io.insert-koin:koin-logger-slf4j:$koin_version")
    ```import io.ktor.server.application.*
    import org.koin.ktor.ext.Koin
    
    fun Application.configureDependancyInjection() {
        install(Koin) {
            slf4jLogger()
            modules(helloAppModule)
        }
    }
    ```Type mismatch: inferred type is Koin.Feature but Plugin<TypeVariable(P), TypeVariable(B), TypeVariable(F)> was expected
    n
    a
    • 3
    • 3
  • p

    Pedro Francisco de Sousa Neto

    05/26/2022, 3:04 PM
    Hey guys, I need advice here. Let’s imagine an android app with hundreds of features. Each feature has one or multiple activities with you N fragments. Each host activity has your Koin module with scope tied to activity. What approach is better? 1. load and unload these activity tied koin modules in each activity host; 2. load and unload these activity tied koin modules in Application class; I think the second option it’s easy to maintain because host activities didn’t care with Koin load/unload and the tied scope can solve this in runtime. But… I don’t know if this case will be less performatic then first option.
    m
    a
    • 3
    • 3
  • m

    Mark Malik

    06/18/2022, 8:32 PM
    Hi Anyone could help with this issue?
    a
    • 2
    • 1
  • r

    Ruben Quadros

    06/25/2022, 6:27 AM
    Hi Arnaud, looks like people are waiting for this feature (including me!). If you are working on something else I would love to raise a pr for a quick fix for the time being. Please do let me know your thoughts 🙂
    a
    • 2
    • 4
  • m

    mbonnin

    09/19/2022, 2:31 PM
    Cross posting: https://kotlinlang.slack.com/archives/C67HDJZ2N/p1663595941423569 . Looks like the latest releases were made with JDK 11 and that JVM-only modules forward that as a required JVM version but there's no real reason to require Java11 ?
    m
    • 2
    • 3
  • l

    Lukas Anda

    12/19/2022, 11:46 AM
    Hi guys, I recently got very interested in experimenting with KSP. So that got me thinking, would you be open to having KSP processor that would verify that all injections are being defined (effectively adding build-time check)?
    a
    • 2
    • 8
  • p

    Pedro Francisco de Sousa Neto

    12/19/2022, 1:26 PM
    I’m upgrading koin library in an Android app from
    3.1.6
    to
    3.3.0
    . When I run app I’m getting this error.
    java.lang.NoSuchMethodError: No static method binds(Lkotlin/Pair;[Lkotlin/reflect/KClass;)Lkotlin/Pair; in class Lorg/koin/dsl/DefinitionBindingKt; or its super classes (declaration of 'org.koin.dsl.DefinitionBindingKt' appears in /data/app/~~aqqlOmEpOuZRMkiV16sAeA==/XXX.YYY.MYPACKAGE.AAA.BBBB-Wnq8EpEHG1vbVsljdmNEow==/base.apk!classes24.dex)
    I’ve already cleaned, rebuild, restarted etc and it isn’t working. Someone as getting this error too? How can I fix it?
  • a

    arnaud.giuliani

    12/19/2022, 1:43 PM
    koin-core -> 3.3.0 / koin-android -> 3.3.1
  • p

    Pedro Francisco de Sousa Neto

    12/19/2022, 2:56 PM
    @arnaud.giuliani I specified correctly right now. But I still getting same error.
    koin_android = '3.3.1'
    koin_core = '3.3.0'
    This can happen If any of my libraries are using a old Koin version (like 3.1.6)? 🤔
    a
    • 2
    • 5
  • e

    Emanuel Moecklin

    12/23/2022, 1:02 PM
    I use
    fragmentFactory()
    to inject Fragments into Activities and that works like a charm. I was wondering if I could use an
    AppComponentFactory
    to do the same for Activities and made a quick prototype:
    val componentFactoryModule = module {
        single<AppComponentFactory> { KoinComponentFactory() }
    }
    
    fun KoinApplication.componentFactory() {
        koin.loadModules(listOf(componentFactoryModule))
    }
    
    class KoinComponentFactory : AppComponentFactory(), KoinComponent {
    
        override fun instantiateActivity(
            cl: ClassLoader, className: String, intent: Intent?
        ): Activity {
            val clazz = Class.forName(className).kotlin
            val instance: Activity? = getKoin().getOrNull(clazz)
            return instance ?: super.instantiateActivity(cl, className, intent)
        }
    
    }
    add to startKoin:
    startKoin {
        componentFactory()
        ...
    and register the factory in the manifest:
    tools:replace="android:appComponentFactory"
       android:appComponentFactory="mypackage.KoinComponentFactory"
    This also works like a charm and I would love this to be part of the library itself but I'm not sure if this is the way to go and how this needs to be changed to play nicely with scopes?
    a
    • 2
    • 1
  • p

    Pedro Francisco de Sousa Neto

    12/23/2022, 7:25 PM
    Scenario:
    1 - Activity using a koin module scope tied
  • p

    Pedro Francisco de Sousa Neto

    12/23/2022, 7:33 PM
    Let me help to know what happens with this scenario, please. Everything will runs OK or dependencies won’t be found because
    scope<ActivityProfile>
    was unloaded by
    ActivityProfile#2
    ?
    1 - A activity class to see users profile, like ActivityProfile
    2 - ActivityProfile has a module tied to it and this activity load and unload this module
    3 - Using the app, ActivityProfile is called twice with distinct parameters like userIDs (so it's a expected behaviour)
    4 - ActivityProfile#1 is in navigation stack and ActivityProfile#2 is in top (user is looking for it)
    5 - User destroy the activity using back button so ActivityProfile#2 calls onDestroy. When this activity is closed user start to look ActivityProfile#1
    6 - ActivityProfile#1 try to access Koin dependencies and ??????
    a
    • 2
    • 19
  • e

    Elio Maroun

    01/03/2023, 9:08 AM
    https://stackoverflow.com/questions/74951871/koin-android-kmm-i-have-nested-scopes-but-injection-is-not-working
    a
    • 2
    • 6
  • e

    Elio Maroun

    01/03/2023, 9:08 AM
    Please if anyone can help
  • c

    Christian Krueger

    01/10/2023, 12:54 PM
    Hi Arnaud, there are two bugs in the koin-android-compat library. 1.
    SharedViewModelCompat
    passed the wrong ViewModelStore (see bug issue) 2. The
    ViewModelCompatgetViewModel
    always sets
    extras = CreationExtras.Empty
    , which causes a missing
    SAVED_STATE_REGISTRY_OWNER_KEY
    I can fix both issues + writing some unit tests.
    a
    • 2
    • 1
  • h

    harshil shah

    01/24/2023, 2:40 AM
    Has anyone used koin in production for kmm library?
    a
    • 2
    • 2
  • p

    Pedro Francisco de Sousa Neto

    02/01/2023, 2:08 PM
    When I use
    private val presenter: MyFeaturePresenter by scope.inject()
    Sometimes I got the crash
    Caused by: java.lang.IllegalStateException: Fragment MyFeatureFragment{e397a0b} (4be986d3-729a-430d-86ee-ee1f657be059) not attached to an activity.
        at androidx.fragment.app.Fragment.requireActivity(Fragment.java:995)
        at org.koin.androidx.scope.FragmentExtKt.createFragmentScope(FragmentExt.kt:38)
        at org.koin.androidx.scope.FragmentExtKt$fragmentScope$1.invoke(FragmentExt.kt:50)
        at org.koin.androidx.scope.FragmentExtKt$fragmentScope$1.invoke(FragmentExt.kt:50)
        at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
    Why? Because this value
    val
    is initializing in
    init
    from Kotlin fragment class. How to avoid that
    private val presenter: MyFeaturePresenter by lazy { scope.get() }
    Is it the expected scenario to Koin lazy injection? 🤔
    m
    a
    • 3
    • 18
Powered by Linen
Title
p

Pedro Francisco de Sousa Neto

02/01/2023, 2:08 PM
When I use
private val presenter: MyFeaturePresenter by scope.inject()
Sometimes I got the crash
Caused by: java.lang.IllegalStateException: Fragment MyFeatureFragment{e397a0b} (4be986d3-729a-430d-86ee-ee1f657be059) not attached to an activity.
    at androidx.fragment.app.Fragment.requireActivity(Fragment.java:995)
    at org.koin.androidx.scope.FragmentExtKt.createFragmentScope(FragmentExt.kt:38)
    at org.koin.androidx.scope.FragmentExtKt$fragmentScope$1.invoke(FragmentExt.kt:50)
    at org.koin.androidx.scope.FragmentExtKt$fragmentScope$1.invoke(FragmentExt.kt:50)
    at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
Why? Because this value
val
is initializing in
init
from Kotlin fragment class. How to avoid that
private val presenter: MyFeaturePresenter by lazy { scope.get() }
Is it the expected scenario to Koin lazy injection? 🤔
fun Fragment.createFragmentScope(): Scope {
    if (this !is AndroidScopeComponent) {
        error("Fragment should implement AndroidScopeComponent")
    }
//    if (this.scope != null) {
//        error("Fragment Scope is already created")
//    }
    val scope = getKoin().getScopeOrNull(getScopeId()) ?: createScopeForCurrentLifecycle(this)
    val activityScope = requireActivity().getScopeOrNull()
    if (activityScope != null) {
        scope.linkTo(activityScope)
    } else {
        scope.logger.debug("Fragment '$this' can't be linked to parent activity scope")
    }
    return scope
}
I think the root cause is the usage of
requireActivity()
inside
createFragmentScope()
.
m

Marcello Galhardo

02/01/2023, 5:37 PM
I’m not sure if Koin can avoid the
requireActivity
, after all the Fragment scope is a child from the
Activity
(see
scope.linkTo
in the code snippet you posted). Ignoring that would break the relationship between these two scopes. Your proposed solution seems off. Aren’t
inject
lazy by default? Wrapping it inside a
lazy
should not change the behaviour. Check the last line of you stack trace
SynchronizedLazyImpl.getValue
. What do you mean by “val is initialized in init”? Do you have a code sample for this statement?
a

arnaud.giuliani

02/06/2023, 10:56 AM
You should use `AndroidScopeComponent`interface. this way just use the i`nject()` function, directly with the right scope
also look at
ScopeFragment
class
p

Pedro Francisco de Sousa Neto

02/06/2023, 1:59 PM
I’m using
ScopeActivity
and
ScopeFragment
. I don’t know yet how can reproduce this error, but I’m getting him sometimes in Firebase Crashlytics. My guess: sometimes fragment is initializing “too fast” and is not attached to activity yet, so requireActivity() throws an exception.
a

arnaud.giuliani

02/06/2023, 5:30 PM
About ScopeFragment it was one problem we had, that scope couldn’t be attached. In latest version it’s now solved
p

Pedro Francisco de Sousa Neto

02/06/2023, 5:43 PM
hummm… I’m using
3.3.1
, what version has it fixed?
a

arnaud.giuliani

02/06/2023, 5:49 PM
you have it 😅
yes, your Activity is not yet attached
this mean you try to do something in a property that is initialized, before any onCreate call
p

Pedro Francisco de Sousa Neto

02/06/2023, 5:57 PM
Yes, that’s the problem! I’m doing something wrong in Koin usage? In my mind, that was a expected usage without crash, of course
I wrote an article in Medium platform about this error and how can avoid it. But, the doubt about usage continues. 🙃
m

Marcello Galhardo

02/06/2023, 8:31 PM
As a rule of thumb, there is no scenario in which you want to do any operation on a Fragment or Activity initialization time. Those components are created with an incomplete state, and only later will receive their respective contexts and required dependencies. That is why they offer you an
onCreate
and that is where your Fragment initialization logic should go to ensure your Fragment is in a safe state. If you use
lazy
, you should ensure it is only called "after"
onCreated
state is reached or you likely will crash.
p

Pedro Francisco de Sousa Neto

02/06/2023, 8:40 PM
I agree totally with you @Marcello Galhardo. And
inject
in Koin usage is lazy and can handle this kind. The problem is when you trigger a combination of
createScope()->requireActivity()
because you just added a
fragmentScope()
. And you’re not expecting that 😅.
Backing to my initial question...
Is it the expected scenario to Koin lazy injection?
I think it’s not expected get a crash when you’re using
scope.injection
. Maybe we need to improve docs, or annotate it with as throwable. I really don’t know right know a better solution to help developers with Koin dev experience.
a

arnaud.giuliani

02/07/2023, 12:54 PM
Maybe we need to improve docs, or annotate it with as throwable.
yes documentation can be improved on this point 👍
p

Pedro Francisco de Sousa Neto

02/07/2023, 1:01 PM
Nice @arnaud.giuliani, I’ll do it ASAP! 😉
a

arnaud.giuliani

02/07/2023, 1:39 PM
great, thanks 🙂 Ping me on the issue/PR
View count: 17