Timeline for How to realize "Tell, don't ask" in an Onion-Architecture for data analysis
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2017 at 6:11 | comment | added | Paul Kertscher | @EmersonCardoso - this kind of makes sense. This might be the part that I got wrong ;) | |
| Dec 15, 2017 at 17:16 | comment | added | Emerson Cardoso | Can you give more examples about what analysis you'll implement? Also: just asking the match object for its contacts to operate on them would be a violation of TDA - the analysis will only be a violation of TDA if you retrieve data, and use them in order to change the state of the match object. | |
| Dec 15, 2017 at 16:11 | comment | added | Paul Kertscher | @EmersonCardoso Thinking about it this could be counted as a TDA violation on its own right ;) | |
| Dec 15, 2017 at 16:11 | comment | added | Paul Kertscher | @EmersonCardoso I have not implemented anything at all, but if I had, I'd - for example - check that no actions that are assigned to a player that is not in the match are added, check that no two player with the same roster number are added, etc. | |
| Dec 15, 2017 at 16:02 | comment | added | Emerson Cardoso | since the match contains business logic - What business rules do you currently have implemented on your Match object? | |
| Dec 15, 2017 at 11:54 | answer | added | Vadim Samokhin | timeline score: 1 | |
| Dec 15, 2017 at 10:50 | history | asked | Paul Kertscher | CC BY-SA 3.0 |