A modern programming language that makes developers happier.

kotlinlang

Possible to use `@Single` annotation on a function? The annotation has function as a target, but when I try creating a top level function to provide singleton, generated code doesnt include it

Looking at the scanning code for the ksp compiler plugin, seems it only scans for classes. <https://github.com/InsertKoinIO/koin-annotations/blob/main/compiler/koin-ksp-compiler/src/jvmMain/kotlin/org/koin/compiler/scanner/KoinScanner.kt#L90|https://github.com/InsertKoinIO/koin-annotations/blob/main/compiler/koin-ksp-compi[…]ler/src/jvmMain/kotlin/org/koin/compiler/scanner/KoinScanner.kt>

Annotation is bit misleading?

it scan also function inside Module classes

just @Single a function that returns a value and you’re done

<https://github.com/InsertKoinIO/koin-annotations/blob/main/sandbox/coffee-maker-module/src/main/kotlin/org/koin/example/test/include/IncludedModule.kt#L12|https://github.com/InsertKoinIO/koin-annotations/blob/main/sandbox/coffee-maker-mo[…]src/main/kotlin/org/koin/example/test/include/IncludedModule.kt>

Is it possible to somehow add everything to default module? If I have multiple packages/project-modules in which I need to create Retrofit services, for each I would need to create new @Module class and then don't forget to add it to `startKoin` . If @Single @Factory and other annotations would work on any top level functions then I don't need to write anything extra. Am I missing something?

<@UT4CRGNRE> From my initial understanding when making this post I also thought `@Single` and `@Factory` annotations worked on top level functions but they didn't (Not sure if that's still the case but most likely not). The annotated functions were only picked up by the processor when inside a class annotated as `@Module` .

Also as far as I know it's not possible to have components generate in module A from a dependent project module B. Ksp scanning seems to happen per project module basis and if no koin module is defined it creates one for you. Think your best bet is creating module classes for your project modules and then including them in your main `@Module` annotation or in `startKoin`

Of course <@U2JKKPMEE> probably has more insight on this :stuck_out_tongue:

Thanks for a reply on an old thread :smile:  Yeah with the current way it works that's the only way I see, which is a shame. I would have really liked to avoid writing modules at all.

&gt; The annotated functions were only picked up by the processor when inside a class annotated as `@Module` .
yes, improvement are coming for this :+1:

&gt; Ksp scanning seems to happen per project module basis and if no koin module is defined it creates one for you. Think your best bet is creating module classes for your project modules and then including them in your main `@Module` annotation or in `startKoin`
Exact :ok_hand: For now, KSP Annotation scanning is done on the current Gradle module