Timeline for How to Validate a Child Object Based on Parent Object's Data
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2020 at 21:12 | comment | added | GHP | I'm not familiar with the term "aggregate root" other than having heard it in passing, but if the end result is that you call the validator function for the parent ReviewProcess then its fine I guess, but it makes me nervous, because each call to validate a Review (by calling the validator on the parent ReviewProcess) now validates all the sibling Review's of the target review (because the parent validator validates all the Review children). This might not be a problem now, but it smells like trouble down the road to me. | |
| Jan 2, 2020 at 15:23 | comment | added | HardCode | Does this represent the "aggregate root" term I've been seeing around? The ReviewProcess is the aggregate root, and just validate the aggregate root and make sure to expose the valid or invalid state of each child Review? | |
| Dec 20, 2019 at 20:49 | history | answered | GHP | CC BY-SA 4.0 |