Skip to content

Keep a multi-day event's end date and match JSON filters by value - #2112

Closed
joepio wants to merge 1 commit into
developfrom
claude/issues-2089-2093
Closed

joepio wants to merge 1 commit into
developfrom
claude/issues-2089-2093

Conversation

@joepio

@joepio joepio commented Oct 6, 2026

Copy link
Copy Markdown
Member

Requested by Joep · project thread

Fixes #2089
Fixes #2093

Before: editing only the end time of a multi-day timed calendar event moved its end date back to the start day (or the next day), so four nights became one. A JSON filter with the exact text of a saved value matched nothing unless its keys were in alphabetical order.

After: the end date stays where it was and only the time changes. A JSON filter value is rewritten with sorted keys and no whitespace when you leave the field, which is how the index stores it, so the text of a saved value matches its row.

How: saveTimes now reads the stored end first and keeps its day offset (daysSpanned / endDayFor in calendarRows.ts); a same-day event whose end is at or before the start still ends the next day. TableFilterValueInput normalizes JSON values through the new canonicalJson. Both have unit tests, and the typecheck and formatter pass. Not run in the browser, so there are no screenshots; neither change adds new UI.


Generated by Claude Code

@joepio joepio self-assigned this Oct 6, 2026
joepio added a commit that referenced this pull request Oct 6, 2026
One tested commit: Cloud Server first uploads and hosting status races (#2108), a multi-day event keeps its end date and JSON filters match by value (#2112), and docs for Personal Data Store, All-in-One Workspace and Local-first Sync Engine (#2109).

Co-authored-by: Joep Meindertsma <joep@ontola.io>
@joepio joepio closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant