Hey all, anyone can answer this question: <https:/...

# koin

[Paolo]

Hey all, anyone can answer this question: https://stackoverflow.com/questions/59772291/koin-how-to-share-class-instances-between-scopes

[arnaud.giuliani]

you cannot describe inner scopes like that

[arnaud.giuliani]

scope block in a scope block I mean

[arnaud.giuliani]

you have to separate it, and pass explicitly it with your resolution in Koin <2.0

[arnaud.giuliani]

https://github.com/InsertKoinIO/koin/blob/master/koin-projects/koin-core/src/test/java/org/koin/core/ClosedScopeAPI.kt#L196

[arnaud.giuliani]

Koin 2.1 solve this with Scope Links to extend visibility of your scope others: https://github.com/InsertKoinIO/koin/blob/master/koin-projects/koin-core/src/test/java/org/koin/core/ObjectScopeTest.kt#L231

[Paolo]

Ok thanks, that's pretty helpful. But was there a design reason why it was done this way? The snippets linked would force me to link the scopes in code. I think it'd be very useful to have this feature right in the dsl.

[arnaud.giuliani]

the DSL is declarative

[arnaud.giuliani]

you will be able to create a scope and nested scopes directly

[arnaud.giuliani]

but generally people using scopes tend to make too much complex things

[arnaud.giuliani]

we don't need scopes to attach things around activities

[arnaud.giuliani]

factory is enough

[arnaud.giuliani]

but depends on your case after that

[arnaud.giuliani]

(of course)

[Paolo]

Well, the idea is that a parent want to share one of its scoped objects with its children. In the case above the DemoEncryptionHandler holds some state that should be maintained during the activity lifecycle. Having a factory for this would render it useless. Then again, the child scope could simply "inherit" the parent scope.

[Paolo]

Also, is the second link you posted current? I cannot find the method linkTo on the scope.

[arnaud.giuliani]

linkTo is in current 2.1.0 alpha