tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/203-signal-and-signalcommand-problemRobotlegs: Discussion 2018-10-18T16:35:19Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/36794812010-11-07T12:57:37Z2010-11-07T12:57:37Zsignal and signalcommand problem<div><p>You can't. You have to make a separate value object that stores the 2 values and pass that.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/36794812010-11-07T17:23:03Z2010-11-07T17:23:05Zsignal and signalcommand problem<div><p>really?? ok...</p></div>sebtag:robotlegs.tenderapp.com,2009-10-18:Comment/36794812010-11-07T18:54:28Z2010-11-07T18:54:28Zsignal and signalcommand problem<div><p>Same with any DI. You can't have ambiguous injections, so to inject base types you either resort to named injection or you wrap things in strong typing. In the case of the SignalCommandMap the injection is automagic, which is great, but you lose the (ugly) naming option. So strong typing is your only option.</p>
<p>It can be as simple as SpecialString() or a vo that holds the properties.</p>
<p>If you really wanted to and can't see the benefit in the strong typing (I like it but you so you know it's not needed) just put the values as named properties on an object or array and dispatch/inject that instead. But you lose all the benefit of type safety.</p></div>Straytag:robotlegs.tenderapp.com,2009-10-18:Comment/36794812010-11-07T19:03:32Z2010-11-07T19:03:32Zsignal and signalcommand problem<div><p>cool thx i already modified the signal and command to take a vo.</p>
<p>thx for the input.</p>
<p>On 7 November 2010 18:56, Stray <<br />
<a href="mailto:tender+da37ba21a924004811679a8eb24e280e92a904a89@tenderapp.com">tender+da37ba21a924004811679a8eb24e280e92a904a89@tenderapp.com</a><<a href="mailto:tender%2Bda37ba21a924004811679a8eb24e280e92a904a89@tenderapp.com">tender%2Bda37ba21a924004811679a8eb24e280e92a904a89@tenderapp.com</a>><br />
</p>
<blockquote><p>wrote:</p></blockquote></div>Sebastien Jouhans