RFC: Add a service injector for service "currying" about breadboard HOT 2 OPEN

Maybe I am missing something, but how is this not the same as the parameterized containers?

from breadboard.

I'd say it's pretty similar to parameterized containers, but parameterized containers hit the problem from the opposite direction. I may even be able to get it to work that way, but it could end up being a big convoluted. The main issue is that I want to use one container to contain the Bread::Board to pass into a job, which might contain several database handles each with their own configuration. All the ways I can think of to make a parameterized container work are more complicated than just currying the services. However, it's quite possible that my understanding of parameterized containers is naive.

What I'm proposing is more like service aliases that modify the service being aliased. Without adding a ServiceInjection class, what I'm proposing could be accomplished via a block injector like this (though, this is not tested, so I might have gotten the details wrong):

        service devdb => (
            block => sub {
                my $s = shift;
                $s->fetch('/ResourceTypes/DB/connection')->get(%{ $s->params });
            },
            dependencies => {
                host => depends_on('devdb_host'),
                port => depends_on('devdb_port'),
                schema => depends_on('devdb_schema'),
                user => depends_on('devdb_user'),
                password => depends_on('devdb_password'),
            },
        );

from breadboard.