calendar · console.warn
a card reschedule did not persist through th...
Printed by calendar, prefixed [lattice], since 1.83.0.
Warnings reference › calendar:writeback-noop
- Identifier
calendar:writeback-noop- Raised by
- calendar
- Since
- 1.83.0
What happened
A move/resize was written through the bound grid's edit.setCells, but the grid refused every cell - the start column (or end column) is read-only, not editable, permission-blocked, unresolvable, or its validation rejected the value. The calendar reverted the card so it never shows a half-applied move.
The fix
Make the start (and end) columns editable and permitted, or correct the value so it passes the column's validation; the card stays where it was until the write can land.
The smallest fix
columns: [{ id: 'start', field: 'start', edit: true, validation: { … } }]
Reference
Covered in full at the API reference.