gantt: {method} on a destroyed controller ignored.

Warnings reference › gantt-destroyed

Identifier

gantt-destroyed

Raised by

Gantt

Since

1.34.0

What happened

A controller method was called after destroy(). A destroyed controller keeps its last schedule so that reads still answer, but every method that would change or draw the plan does nothing: the call returns the stale schedule (or null for a mount) and nothing is recomputed or rendered. The commonest cause is a framework teardown that destroys the controller while an async callback is still in flight.

The fix

Stop calling the controller once you have destroyed it - cancel timers and unsubscribe in the same teardown - or build a new controller. The method that was called is named in the line.

Reference

Covered in full at the API reference.