https://github.com/InsertKoinIO/koin/issues/577 - in work

@arnaud.giuliani can you upgrade to branch 2.1.0 to the latest master?

is it

synchronized

/ monitor expression?

HI. @arnaud.giuliani, what about support Android Saved State for Viewmodel?

I have problem in 2.0.1 that I can’t have two dependencies of different types but with the same qualifier in the graph. For now I’ve solved this with creating more complex qualifiers, but it looks realy bad. It it possible to support dependencies of different types but with the same qualifier ?

@arnaud.giuliani Take a look my PR, plz… https://github.com/InsertKoinIO/koin/pull/667 https://github.com/InsertKoinIO/koin/pull/681 Well, someone else note that there are no comments 🙂

Before going to Beta, can be good to check 2 things: • Better usage of Enum for Qualifier • Gradle plugin to help verify graph

After this, 2 major features : • going Multiplatform • working with Arrow Meta to help write DSL or produce IDE checks

@arnaud.giuliani https://github.com/InsertKoinIO/koin/pull/692 - First draft. I will add changes to this PR, according to the list.

Hi @arnaud.giuliani . What do you think about possibility to include module into another modules? Like in Dagger.

The second issue is constructor lazy & provider injection into constructor. It’s bad to have required dependencies of a component into properties because DI library can’t do that

@arnaud.giuliani in GitHub can you specify developers (field “Assignees”)? I would take this one: https://github.com/InsertKoinIO/koin/issues/694

OK

Hey, I am Mohi from Bangladesh. The Country Lead of Bangladesh Kotlin User Group. I want to be a contributor to Koin. This is really awesome. I would like to be a part of it. I need some initial help to start. I believe @arnaud.giuliani can help with it. 🙂 Thanks.

finally, pushed last fixes for 2.1.5 - https://medium.com/koin-developers/unboxing-koin-2-1-7f1133ebb790

What about features and performance ?

Hi all, I have a question. In my application, I use the navigation library and in the navigation library graph, I have 3 fragments. Koin has a function for creating shared ViewModel only for these 3 fragments not for all fragments in the activity.

there is several ways to help: • Issue solving & Bugfix • answer some questions • add new feature

I'm trying to sync the project but I'm getting this error: FAILURE: Build failed with an exception. * What went wrong: New Gradle Sync is not supported due to containing Kotlin modules

Hello everyone, I'm using

stateViewModel

in my project, but I have the same problem related here https://github.com/InsertKoinIO/koin/issues/787 and I opened a pull request fixing that (https://github.com/InsertKoinIO/koin/pull/795).

I was wondering if anybody has some ideas/feedbacks regarding this. In our project we use the described code on top of Koin for more safety.

Hi, I opened an issue for a bug and also provided possible solutions here https://github.com/InsertKoinIO/koin/issues/803. I would like to open PR for this if possible as well :)

Hi everyone, viewing files with lots of koin factories, singles or scoped lambdas makes my Android Studio working very slow. Does anybody have any idea how to fix this? Or it's only my problem?

Hi There, I wanted to know is there any Android version limitation to use Koin?

Hi everyone, Recently I had tried to implement Koin in my project. After trying Koin, I realized how concise and simple the implementation is. The time for me to learn using Koin is pretty fast, comparing to Dagger 2. But there's something that keeps bothering me. I saw an article mentioned that Koin isn't using the DI pattern, rather it using the Service Locator pattern. My question is, why Koin use the Service Locator pattern? And is that matter which pattern to use? Thanks a lot.

ping me if you want to participate, I will continue to post some current updates

Hi Everyone, I'm facing a bug related to the

koin

implementation of the

FragmentFactory

. Basically, if you inject a

ViewModel

in the constructor of the

Fragment

, this one will be instantiated again if you rotate the screen. This bug is reproducible only injecting the

ViewModel

via the fragment constructor but is not possible to reproduce it injecting the

ViewModel

via the lazy extension

viewModel()

Let me know if you are already aware of this bug or I can open an issue on Github.