Timeline for Is circular reference with Typescript array properties bad design?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2019 at 17:58 | answer | added | Andy | timeline score: 3 | |
| Jun 10, 2019 at 15:22 | answer | added | JimmyJames | timeline score: 1 | |
| Jun 10, 2019 at 15:15 | comment | added | Ray | Fair enough, looking to see if there is a eloquent solution. | |
| Jun 10, 2019 at 15:14 | history | edited | Ray | CC BY-SA 4.0 | added 127 characters in body |
| Jun 10, 2019 at 15:11 | comment | added | JimmyJames | Do you want options for solving this problem? Right now the way you have put it, it's a yes/no question. I suggest editing it if you want help with the solution. | |
| Jun 10, 2019 at 15:00 | comment | added | Ray | I understand the benefit of enforcing this in a A to B / B to A scenario. But in a situation where the parent has a list of children and the children knows about its parent, I see it as a bad limitation. | |
| Jun 10, 2019 at 14:58 | comment | added | JimmyJames | Compared to some other language such as Java, this is a limitation but other languages also don't allow this. Whether it's a 'bad' limitation is a subjective question. | |
| Jun 10, 2019 at 14:54 | history | asked | Ray | CC BY-SA 4.0 |