Timeline for Separation of concerns: persisting complex types
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2023 at 14:41 | vote | accept | alturkovic | ||
| Nov 26, 2023 at 10:15 | comment | added | alturkovic | This is the closest to what I had in mind. Introduce a serialization module with HandlerSerializer, put core implementations in the serialization module, but have all other modules be self-contained. Meaning, each other module should also depend on the serialization module and add their HandlerSerialization implementations directly in it. That way I could avoid having persistence directly in core. Hiwever, you raise a valid point about private fields. I might just simplify and have persistence directly in core. Thanks for the advice. | |
| Nov 26, 2023 at 7:54 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 146 characters in body
|
| Nov 26, 2023 at 7:26 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 338 characters in body
|
| Nov 26, 2023 at 7:21 | history | answered | Doc Brown | CC BY-SA 4.0 |