undermark5
undermark5
A work around is to declare `operator fun invoke() = this` on the objects. It may not be pretty, but it is a valid work around (koin really should only...
This seems like something similar to #107 would work here.
Not exactly. Last I checked #107 only impacted module definitions, not dependency definitions. That is that I don't think that #107 in it's current form provides a solution for this...
Interesting, I had the issue with it being an object, then it was resolved when it was made into a class. I will note that I was also having issues...
Is it ever necessary to reference the module outside of instantiating Koin/multiple times? If so, couldn't this proposal cause problems? I'm not certain that referencing a module multiple times is...
Isn't the point of the default to be a fallback in case a bean definition isn't otherwise provided? How do they work without annotations? The specific use case I'm looking...
Maybe this is overly complex and it also may not work out like I'm thinking, but something like this seems like it might work. ```kotlin interface DefaultGenerator { fun generate():...
>:thinking: begins to be tricky. The initial case is to use Koin property if there is no default value right? Default to anything provided by koin, falling back only if...
There may be some expanded/interesting use cases for this in relation to #54.
> I'm stuck on some dev about accessing the default value expression. I'm waiting some support on this point 👍 I'm not sure I understand what you're saying? Are you...