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
Is your feature request related to a problem? Please describe.
I am developing a ksp processor for generating a koin module from ktorfit declarations. https://github.com/dshatz/ktorfit-koin
The problem is that koin config check doesn't allow this. The error I get is: Fix your configuration: add @Module annotation on <Module class generated by ktorfit-koin>
Describe the solution you'd like
Optionally disable @Module annotation presence check (for generated code?). Or implement some plugin mechanism?
Describe alternatives you've considered
Disabling koin config check.
Target Koin project
Koin annotations, to be specific config check part.
The text was updated successfully, but these errors were encountered:
Check the part with markerName.
Basically I manually generate an empty class for each ktorfit-koin module so that koin config check doesn't complain about missing @module annotation on those.
Not sure if that is relevant to koin-annotations anymore.
But could you explain please what's the purpose behind those generated empty classes (they end with Def from what I remember)?
Is your feature request related to a problem? Please describe.
I am developing a ksp processor for generating a koin module from ktorfit declarations.
https://github.com/dshatz/ktorfit-koin
The user creates a class:
My library generates:
Then, import the generated module into a normal Koin module.
The problem is that koin config check doesn't allow this. The error I get is:
Fix your configuration: add @Module annotation on <Module class generated by ktorfit-koin>
Describe the solution you'd like
Optionally disable
@Module
annotation presence check (for generated code?). Or implement some plugin mechanism?Describe alternatives you've considered
Disabling koin config check.
Target Koin project
Koin annotations, to be specific config check part.
The text was updated successfully, but these errors were encountered: