You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there 👋
Thanks for the fantastic library - made it really easy to convert an android app using dagger to a multi-platform app using kotlin-inject. I couldn't wish for anything more.
Background
We need to have our component expose a type Foothat is also used inside the component by another type Bar. This did work when the provisioning was declared as a property on the component, but seems to not work when instead using a function. It looks like the generated code still tries to call the function as a property. At first I thought we are having caching issues here.
Hello there 👋
Thanks for the fantastic library - made it really easy to convert an android app using dagger to a multi-platform app using kotlin-inject. I couldn't wish for anything more.
Background
We need to have our component expose a type
Foo
that is also used inside the component by another typeBar
. This did work when the provisioning was declared as a property on the component, but seems to not work when instead using a function. It looks like the generated code still tries to call the function as a property. At first I thought we are having caching issues here.Minimal example
I created a minimal example repo here: https://github.com/degill/kotlin-inject-fun-bug-example
But it boils down to these lines:
Actual behaviour:
The code that gets generated tries to call
provideFoo
as a property:Expected behaviour
In the
README.md
it says using either way should work:But maybe I overlooked something.
The text was updated successfully, but these errors were encountered: