Timeline for How to restrict the construction of a domain object to an external service?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 12, 2023 at 4:49 | history | suggested | CommunityBot | CC BY-SA 4.0 | improved details |
| Mar 2, 2023 at 12:24 | review | Suggested edits | |||
| S Mar 12, 2023 at 4:49 | |||||
| S Feb 24, 2023 at 13:47 | history | suggested | CommunityBot | CC BY-SA 4.0 | Details improvement. |
| Jan 25, 2023 at 15:59 | review | Suggested edits | |||
| S Feb 24, 2023 at 13:47 | |||||
| Jan 25, 2023 at 13:26 | comment | added | Douglas Monteiro | Hi! Thank you for answering. About the answer, how could I restrict the construction to the fooProvider? I can see that it will need a reference of AbsoluteFoo factory or builder, but how can I make sure that only the fooProvider service can create instances of AbsoluteFoo? Should I do this at all? My intention is to avoid developers creating instances of AbsoluteFoo by means other than the fooProvider (this service could be mocked for the tests, so the test part is ok). | |
| Jan 25, 2023 at 9:59 | history | edited | user426115 | CC BY-SA 4.0 | Formatted text |
| Jan 25, 2023 at 9:58 | history | edited | user426115 | CC BY-SA 4.0 | Formatted text |
| S Jan 25, 2023 at 9:57 | review | First answers | |||
| Jan 25, 2023 at 10:14 | |||||
| S Jan 25, 2023 at 9:57 | history | answered | user426115 | CC BY-SA 4.0 |