Claude 69aeb4aabb feat(rundown): clear a mixed field explicitly, cover both fixes with tests ...

Emptying a field which holds different values across the selection does not
submit, otherwise focusing it and tabbing away would wipe every entry. That
left no way to clear such a field, so text fields now offer an explicit
Clear action, shown only while the entries disagree. Once they agree the
field can be emptied by hand and the action is withdrawn.

Both of the fixes which multi edit depends on were unguarded, so the logic
moves into pure helpers alongside the existing hook helper convention:

- shouldSubmitValue covers an unknown initial value being submitted as an
  empty string
- applyPatchToEvents covers the optimistic batch update, whose signature now
  makes the original mistake of spreading the request body unrepresentable,
  and pins the custom field merge

Both tests were confirmed to fail against the original behaviour.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PDETGBrhwgAqgTHjmrmJGJ

2026-07-25 12:49:47 +00:00

..

cli

bump version to 4.11.0

2026-07-18 15:24:25 +02:00

client

feat(rundown): clear a mixed field explicitly, cover both fixes with tests

2026-07-25 12:49:47 +00:00

electron

fix: timer-legacy view not served in desktop distributions

2026-07-19 10:02:45 +02:00

resolver

bump version to 4.11.0

2026-07-18 15:24:25 +02:00

server

fix: issue where a countToEnd would lead to incorrect expected times (#2149)

2026-07-25 11:22:24 +02:00

spec

Deps migration (#1988)

2026-03-08 16:22:12 +01:00