Current structure was defined before the app fully adopted SwiftPM, and is a little confusing + source of a few bugs for EF 26. Reworking the timeline controller to use the Schedule object from the model directly and apply specifications in place of the repository type + various adapters will streamline its implementation and reduce the amount of untested code (which has partly led to a few of the aforementioned bugs).
Current structure was defined before the app fully adopted SwiftPM, and is a little confusing + source of a few bugs for EF 26. Reworking the timeline controller to use the Schedule object from the model directly and apply specifications in place of the repository type + various adapters will streamline its implementation and reduce the amount of untested code (which has partly led to a few of the aforementioned bugs).