Timeline for How do I encapsulate domain logic and preserve state in DDD+Clean Architecture?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15 at 19:26 | history | edited | CPlus♦ | CC BY-SA 4.0 |
Improved flow, removed unnecessary text, punctuation
|
| Aug 15 at 19:21 | history | edited | CPlus♦ | CC BY-SA 4.0 |
Improved flow, removed unnecessary text, punctuation
|
| Jun 5 at 5:01 | answer | added | VoiceOfUnreason | timeline score: 1 | |
| Jun 4 at 18:50 | comment | added | Greg Burghardt | RE: don't pass domain objects --- there is some context missing from that statement. There are situations where passing domain objects around is not only the best way, but it might be the only way to accomplish something without incurring a migraine. Be careful about absolute statements in software engineering. | |
| Jun 4 at 13:24 | comment | added | royneedshelp | Why immutable? On purely practical level the angualr framework won't detect changes on objects that are mutated. On a purist level, I've just always seen it as an anti-pattern. (Thanks for the scrutiny - always useful when learning) | |
| Jun 4 at 13:23 | comment | added | royneedshelp | R Martin (Clean Architecture) recommends against passing domain objects around as they have different purposes and may diverge. | |
| Jun 4 at 13:18 | review | Close votes | |||
| Jun 14 at 3:03 | |||||
| Jun 4 at 13:09 | comment | added | Bart van Ingen Schenau | Why do you state that passing domain objects around is nor recommended? and why would a domain object need to be immutable? | |
| S Jun 4 at 12:45 | review | First questions | |||
| Jun 8 at 19:50 | |||||
| S Jun 4 at 12:45 | history | asked | royneedshelp | CC BY-SA 4.0 |