Reminders

lightweight tag ab67460d0fea3b90b092eb513a827dedf9670591 v12.9.0
Author:    Pat George <patgeorge@meta.com>
Date:    Thu Aug 27 11:03:29 2026 -0400

commit ab67460d0fea3b90b092eb513a827dedf9670591
Author: Pat George <patgeorge@meta.com>
Date:   Thu Aug 27 11:03:29 2026 -0400

    Release v12.9.0

commit a8f6319ff3f3e2167c5f7b662f3fba58e6b4e404
Author: Pat George <patgeorge@meta.com>
Date:   Thu Aug 27 11:02:54 2026 -0400

    Refresh README features and UI sections

    The UI section documented click-to-evaluate and Alt+Click-to-delete,
    neither of which has existed for a while, and FEATURES listed only the
    snooze button -- missing cross-character reminders, edit, enable/disable,
    and What's New.

commit 3db0129ac4f436ab0e2c0333dfc32283cae48e8d
Author: Pat George <patgeorge@meta.com>
Date:   Thu Aug 27 11:02:54 2026 -0400

    Clear a snoozed reminder's row from the popup

    Dismiss removed its row and reflowed; snooze just greyed the button out
    and left the row sitting there. Snooze everything and you were left with
    a full-size popup of dead rows, a header count still claiming they were
    live, and no way to close it but the frame's X.

    Snooze now clears its row too, after leaving "Snoozed!" up briefly so the
    click still registers visually. The row token guards against the pooled
    row being rebuilt for a different reminder inside that delay.

commit bcdf997ca2c5568dd3564beaa0b19cc4f59d4292
Author: Pat George <patgeorge@meta.com>
Date:   Thu Aug 27 11:02:54 2026 -0400

    Build reminder params directly instead of round-tripping a string

    The create form built a comma-delimited string that was immediately
    parsed back into a table on the next line. Nothing else ever consumed
    it -- reminders are stored as a table and WoW serializes SavedVariables
    itself -- so the format bought nothing and cost two bugs:

    - commas had to be stripped from the message and value, so "Buy flasks,
      potions" silently lost its comma
    - the day index came back as a string ("3") instead of the number the
      dropdown supplied, which is why reads of it are littered with
      tonumber()

    Existing reminders are unaffected; every read already coerces, so old
    string days keep working alongside new numeric ones.

commit d9f2af7b80e59ed77258d733d6070e046d242d28
Author: Pat George <patgeorge@meta.com>
Date:   Thu Aug 27 11:02:41 2026 -0400

    Make dismissing another character's reminder persist

    Dismissing an alt's reminder only hid the popup row, so the next
    evaluation -- a /reload, most obviously -- surfaced it again. Your own
    reminders didn't have this problem because firing one already advances
    its schedule.

    Record the dismissal against that character in its own table, separate
    from char.reminders, and skip the row until the reminder next comes due.
    Keeping it out of the schedule preserves the #21 rule that you can't
    clear an alt's chore from your main: log in as them and it's waiting.