Hi everyone, I want to know that we can't pass `Context` in viewModel parameter as it leads to memo...

# android

[Zaki Shaikh]

Hi everyone, I want to know that we can't pass Context in viewModel parameter as it leads to memory leak but if I have a viewModel and A repository in its constructor injection so can I inject context in repository and if yes then why it won't lead to memory leak as it does in viewModel. Thank you

[Alexej Hlinka]

why do you need context in repository ? ....honestly i would avoid passing context to non-ui layers at all costs 😄

[chanjungskim]

Not only viewModel but most of it.

[chanjungskim]

Not only context but also all the things that can be connected to other class such as Listener.

[chanjungskim]

you can inject context with di library. But you should reconsider if you really need the context for the business logic. Context is normally, for intents, accessing resources or managers, services, etc.

[Zaki Shaikh]

I need to access shared preferences in repository so how can I do this?

[chanjungskim]

You can inject context to the Preference class.

[chanjungskim]

And inject the preference class into the ViewModel. Then you won't need context in viewmodel

[Zaki Shaikh]

Yes but if I am injecting which is using context and pref class is being used in repository and repository in viewModel so does lead to memory leak or not, I just want to know.

[chanjungskim]

If you use hilt, it doesn't lead memory leak

[Zaki Shaikh]

Yes I am using hilt

[Sam Pengilly]

I think more specifically it doesn’t lead to leaks because:
1. It’s the application context that’s being injected, not an activity context (which could leak if the activity is destroyed whilst the viewmodel lives on)
2. Dagger/Hilt manages the lifecycle of components according to the scopes used. Creating a singleton of some retrofit service built using an application context is normal and won’t lead to leaks. It’s something that is expected to live for the whole application lifecycle