Timeline for Extracting pattern and simplifying testing
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 30, 2013 at 18:34 | vote | accept | abatishchev | ||
| Dec 30, 2013 at 14:54 | comment | added | Mark Brackett | If you make it strongly typed, you'll end up having to specify the exact steps as delegates (as others have mentioned). You could do a BasePipeline and then derive an XElementPipeline from it with the steps to prevent having to respecify it in your tests. You may also want to look at Task.ContinueWith which could be useful for chaining with or without async behavior. | |
| Dec 28, 2013 at 6:35 | comment | added | abatishchev |
The post under last link is in top of Google for "c# pipes filters generic". It's good but (besides can be refactored nicely with ops.Aggregate(input, (i, op) => op.Exec(i))) its weak part is all input and output parameters have the same type T what makes Aggregate applicable to it and it not applicable to my case as 1:1.
|
|
| Dec 28, 2013 at 4:18 | vote | accept | abatishchev | ||
| Dec 28, 2013 at 7:22 | |||||
| Dec 27, 2013 at 20:55 | comment | added | abatishchev | But a question please: how to make it generic? I tried to roll out something similar by myself but stuck making it generic. | |
| Dec 27, 2013 at 20:54 | comment | added | abatishchev | Looks like that's exactly I was looking for. Awesome, thanks! | |
| Dec 27, 2013 at 20:23 | history | answered | Mark Brackett | CC BY-SA 3.0 |