Now that dev-master has the ability to automatically map commands based on custom strategies, it might be nice to add a tactician:debug command which dumps which handlers commands are routed to.
In terms of implementation, we should probably populate this info into an object at the end of the CommandHandlerPass, then maybe see if we can serialize it into a single parameter at the end of the container.
Alternately, we can serialize the Routing object itself and change the locators to read from it at production time (they'll need a new constructor param to limit themselves to a single bus though).
Now that dev-master has the ability to automatically map commands based on custom strategies, it might be nice to add a tactician:debug command which dumps which handlers commands are routed to.
Something like:
In terms of implementation, we should probably populate this info into an object at the end of the CommandHandlerPass, then maybe see if we can serialize it into a single parameter at the end of the container.
Alternately, we can serialize the Routing object itself and change the locators to read from it at production time (they'll need a new constructor param to limit themselves to a single bus though).