it’s a dangling observable

i am certain

right..., no way these are sharing a

compositeDisposable

is there?

that’s how it used to be, that’s the way it used to work

i cant get hastebin to work

well think we're a bit off topic, feel free to DM me, or start a thread

yea it is very offtopic

ah I can DM

ok

ok so this call

val mapper: CarMapper by inject {
        parametersOf(EndResultSubscriber())
    }

at the beginning of the viewmodel, is causing the endcase to be triggered

my mapper is a collection of usecases that only awaits the end subscriber, which gets injected into it

when i make that call, its populating liveData with something and the call in my screen is getting live data coming up empty for that first time

how can I inject it without calling it

@arnaud.giuliani on Koin 1.0 we could have a

module

with a name that we would release it whenever we wanted. Now with Koin 2.0 I see that there is one step added, if we want to use the Scope API. We need to manually create the scope and then access parts of the module holding the scoped components. This forces us to inject the codebase with more places where we need to actually

close()

and

create()

a Scope, making it possible to miss something. Why can’t we have a same behaviour and just auto-create the scope of the requested module and only have to manually

close/drop/release

it whenever it fits ?

the thing is ... we can have several instance of the same scope

you will have to create a scoped for several scopes & deal with it

the old API was a bit simplistic 😕

But the new API does not provide a clear path for migrating this!

It just enforces the Scope API 🙂

yeah the idea is to stop auto magic stuffs

and try to bring complete scope mechanisms

and make it easy if possible

for you

imagine that you replace your old module declaration with scope

it will be the same: describe a space where I master time for components

Think of a network module where I need to always manually create its scope and close it in order to specifically drop one of the scoped components!

I can safely close it anymore

because I will need to also create a scope

you can retrieve your scope instance from anywhere