Hi, is there any best practice for how to define koin modules that might require configuration to ch...
r
RJ Garcia
11/25/2025, 5:47 PMHi, is there any best practice for how to define koin modules that might require configuration to change the behavior or actual instances of the registered services?
An example I have is a module that registers SSLContext and related services. In prod, I might have a service that will actually try and refresh the ssl context on a schedule, but in dev environment i might not need that. Or I might want to configure to load cert files from one location in deployment context, but look at a separate set of folders for the cert files in a different deployment context.
My current approach is to have "*ModuleConfig" class that i register a default version of in the module, and then callers can then redefine their own *ModuleConfig instance if they need to override things in different environments.
This isn't super ergonomic with koin though, and I don't see any docs or discussions around this. So I wonder if i'm thinking about this incorrectly