For Smart Gantt, the cleanest approach is to enable the built-in editing features and make your data model the single source of truth.
A typical production pattern is:
Enable the required editing options (task editing, drag-and-drop, resizing, etc.) in the Gantt configuration.
Listen for the component’s edit/change events (such as task updates, resize, or move).
Update your application state or send the changes to your API from those event handlers.
When the server responds, update the underlying data source instead of forcing a full component refresh. This keeps the UI and your data synchronized.
If you’re seeing changes only after a manual refresh, it’s usually a sign that the component’s data source isn’t being updated reactively after edits. Rather than recreating the Gantt instance, update the affected task in your data model and notify the component of the data change using the framework’s reactive state management (or the component’s data update API, depending on your setup).
This event-driven approach scales well for both static and API-backed data, minimizes unnecessary re-renders, and provides a much smoother editing experience in production.
Regards,
Markov
.
