Map services with init variables?

[mikegrogan]

Is there a recommended way to pass in config settings (e.g. get("datasourcename") ) inside a service?

You can't just call get("datasourcename") inside the service it looks like. If I try to do something in an init function it seems to just find other services and auto wire it up. https://guides.wheels.dev/v4-0-0/digging-deeper/dependency-injection-usage/#auto-wiring-init-parameters

Can I also pass in my own variables to an init? Inside services.cfm I can dump a get variable.
writeDump(var=get("datasourcename"),abort=true,label="");

But I'm not sure if it's possible to pass anything in the service mapping
local.di = injector();
local.di.map("emailService").to("app.lib.emailService").asSingleton();

I see wirebox has something like initWith that might be the closest thing to what I'm thinking.
initwith: https://wirebox.ortusbooks.com/configuration/mapping-dsl/dependencies-dsl

I'm just exploring. This isn't super urgent. Or maybe it's not even a recommended approach.

As a workaround, I can still call a function inside my service and pass in a get variable. It's just maybe not as clean.

[bpamiri]

Hey Mike — there isn’t a WireBox initWith on our mapping DSL, and that’s by design so far. map().to().asSingleton() only stores a name → path (+ lifetime). Auto-wiring then looks at init() parameter names and fills any that match a registered service. A config key like dataSourceName isn’t a mapping, so it never gets injected — and if you name an init arg after some other service, that’s why you see those get wired instead.

Two other wrinkles: get() is a Wheels helper, not a global on a plain app/lib CFC, so inside the service you want application.wo.get("dataSourceName"). And if you pass a non-empty initArguments struct to getInstance(), auto-wiring is skipped entirely.

Recommended pattern (this is what the DI usage guide shows for JWT, etc.) is a tiny factory whose init() reads config:

// app/lib/EmailServiceFactory.cfc
component {
    public any function init() {
        variables.instance = new app.lib.EmailService(
            dataSourceName = application.wo.get("dataSourceName")
        );
        return this;
    }
    public any function build() {
        return variables.instance;
    }
}

// config/services.cfm
local.di = injector();
local.di.map("emailServiceFactory").to("app.lib.EmailServiceFactory").asSingleton();
// callers: service("emailServiceFactory").build()

Your “pass get() into a method from the controller” workaround is also fine, and often cleaner — keeps config at the edge. If you want mapping-time initWith, say the word and I’ll open an issue; not something I’d bolt on without a real need.