Expand description
Timers running locally, kept between runs.
A timer is not a Tracker object: there is no endpoint for “started working”, only for “worked this long”. So the start is remembered here and turned into a worklog on stop, which is the whole mechanism.
Two decisions worth stating. It lives beside the config rather than in a
dotdir of our own, because it is derived state of the same account and
nobody should have to learn a second place to look. And it is keyed by
organisation as well as by issue: PROJ-1 in two organisations is two
issues, and stopping the wrong one would log somebody else’s time. By
organisation rather than by profile, because two profiles onto the same
organisation are two ways of saying the same issue — a timer started through
one should stop through the other.
Structs§
Functions§
- path_
for - Where the timers live: beside the config, like the queue cache.