The only way to get the current activity context is using parameters when it is being injected?

# koin

[Javier]

The only way to get the current activity context is using parameters when it is being injected?

[tynn]

You could also use a scope providing it. But eventually it'd be best to not provide it as a dependency.

[Javier]

the problem I have is I need the activity context to get the colorPrimary attribute

[tynn]

So you basically need the theme. Might be a bit safer to inject.

[Javier]

The problem is theme is changing

[Javier]

So I guess androidContext() is getting the app context, which has AppThemeOne, but I was changing the theme later to AppThemeTwo, but androidContext() can't know that

[tynn]

You could wrap everything with a color provider you use in the UI where you have the Context

[tynn]

You're right, androidContext() binds the Application

[Javier]

But I will have the same problem if I keep using androidContext() for this colorProvider

[Javier]

Should be great to have a way to get the activity context out of the box

[tynn]

I didn't mean to use the Context within the provider, but rather have the provider implement (Context) -> Int

[tynn]

The you just call colorProvider(context) from where you actually have the context.

[tynn]

Using the Activity as dependency is dangerous and discouraged by many. That's why I don't mind that it doesn't exist.

[tynn]

If your dependencies are bound to this activity, it should be fairly easy to create a scope and inject the activity there. Like that instance might not leak.

[Javier]

I will take a look, thank you 🙂