I have in mind two options:

  • Code in the class being saved/loaded. The flows for each entity/model are in the same place, so it’s easy to just have one file open to see all the functionalities of that class, but this means having more code in a single file.
  • Code in a dedicated class (like a factory)
    This makes each file smaller, but spreads flows of a single model into different parts of the repo, also because I’m thinking of having a directory /src/models and another like /src/export (or serialize)

What do you guys think?
What’s your preferred way to organize the save and load flows?

  • MajorHavoc@programming.dev
    2·
    1 day ago

    Related code should go together as much as possible, for maintainability.

    If this results in too much code together, it’s time to think about other ways to structure the code so that each thing the user can do fits into as few files as possible, but not too many things the user can do share a file.