Document parameterized container names about breadboard HOT 4 CLOSED

Yes it is intended behavior, because there actually is no container X, that is the name of the parameterized container. The result of ->create is actually an entirely new container (essentially a clone of X).

from breadboard.

Okay, I think I understand now. Your answer helps me read between the lines in the manual a bit. The docs say, "Parameterized containers can also be nested, here is an example of an Application container that expects a Logger." It then shows an example of doing so.

Reading between the lines a bit more, it seems like that statement ought to be strengthened to a full recommendation rather than a "you can do it this way."

The alternative to construct a parameterized container and then your application container something like this:

my $app = container 'App' => as { ... };
my $my_db_logger = $db_logger->create(
    DBConnInfo => $db_conn_info
);
$app->add_sub_container($my_db_logger->clone(name => 'Logger'));

It works and does nearly the same thing, but is not nearly so nice.

from breadboard.

Though, the latter might be better in a case like mine, where I'd like to progressively build the main application container because I'm only going to need a subset of the full configuration depending on how the app is being run and calculating the full configuration could be pretty expensive.

from breadboard.

The doc patch has already been merged to master.

from breadboard.