Tisty 0.13.0
A deadline finally does something. You could always set one, it was stored, it
travelled between your machines and it was printed on the card — and nothing ever
asked it a question, so tisty ls overdue skipped a task whose limit ran out
yesterday. It does not any more. Planning to get to something next week does not
un-expire a limit that is already gone.
The hour a routine gets closed at now stays where it happened. That chart read
every closing in whatever zone you happen to be in, so a week abroad slid the bars
with nobody touching them; each closing carries its own zone from here on. And the
turns you tick days later are left out of it, because what they would show is the
hour you remembered, not the hour you did it — the same reason they no longer
claim you were late, and now they also count in the month they covered rather than
the month you got round to them.
Underneath, the log grows a version. Nothing you have written changes and nothing
is lost. Until now a Tisty that met an entry it did not recognise refused to read
the store at all — the right instinct for anything that alters what you already
have, far too blunt for an entry that only adds. From here on whoever writes says
which it is, and a later Tisty can step over what it does not know instead of
stopping. It had to go out before the thing it is meant to tolerate exists, which
is why it ships now with nothing yet to tolerate.
Every entry also records the zone it was written in, which is what makes the hour
above hold still. Your journal already did this; nothing else did. It only fixes
what gets written from here: what is already on disk never knew, and cannot learn.
If you use Tisty on more than one machine, update them together. A version
before this one will not read what this one writes, and will stop syncing rather
than bring across half a store.
What's Changed
- feat!: schema 7, with a door for the operations that do not exist yet by @rgdevment in #6
Full Changelog: v0.12.3...v0.13.0