Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Change schedule data on global scope edit #262
The problem is that global scope changes aren't necessarily made "from the start" and thus not all global changes should warrant a change to the schedule itself, but yeah, there should be a special case where globally changing the first spawn of a schedule changes the schedule itself.
(from [fb634ecb7d07]) [#262 state:fixed] Schedules are now updated by global changes when appropriate.
When a global change becomes the first spawn of a schedule, it replaces the ref txn of the schedule. This is to avoid the confusing situations where the schedule transaction would be different from all its spawns, and that changing a schedule would have no effect on its spawn (a new global change would be required).
Also, deleting the first spawn(s) of a schedule will make its start date move forward.