There are currently more than one "type" of time in the scheduler and their definitions are core to the data models for schedule data types. While not horrible, they remain confusing to think around if, at minimum, because the semantics of their naming, interchange between using newtypes vs type aliases, and how they get used by sum types in schedules. Refining them down and or even eliminating entire types is required to achieve a basic MVP.
Assignees
@ejmg @ArcTangent20EggsEggs
Background
24 is being broken up into even smaller task items to achieve a functional MVP, and this is one of those items.
Constraints and Assumptions
TBD
Blockers
The implementation of #35 is heavily effected by this issue.
Refine data model of time data types
There are currently more than one "type" of time in the scheduler and their definitions are core to the data models for schedule data types. While not horrible, they remain confusing to think around if, at minimum, because the semantics of their naming, interchange between using newtypes vs type aliases, and how they get used by sum types in schedules. Refining them down and or even eliminating entire types is required to achieve a basic MVP.
Assignees
@ejmg @ArcTangent20EggsEggs
Background
24 is being broken up into even smaller task items to achieve a functional MVP, and this is one of those items.
Constraints and Assumptions
TBD
Blockers
The implementation of #35 is heavily effected by this issue.
Design Changes
TBD
References
TBD