gantt: this plan reads {fields} through a `f...

Warnings reference › gantt-edit-mapped-field

Identifier

gantt-edit-mapped-field

Raised by

Gantt

Since

1.59.0

What happened

The plan maps one or more scheduling fields through a reader *function*. A function says how to read a value and cannot say how to write one, so applyEdit has nowhere correct to put the new value: it writes the canonical property (start, end, …) instead, and your reader goes on returning the old value. The edit therefore appears to do nothing, which is why it is named rather than left silent.

The fix

Map those fields to a field *name*, which round-trips both ways. Where the value genuinely has to be computed, write it into your own row and feed the row back with rows.apply.

The smallest fix

createGantt({ tasks, fields: { start: 'plannedStart' } });   // a name, not a function

Reference

Covered in full at the API reference.