Our state of the art Gantt chart


[REACT] Performance Issues with Large Datasets and Errors in Bryntum Gantt Chart

Post Reply

Post by mats »

Not yet I'm afraid - we'll prioritize them shortly. Regarding this one: https://github.com/bryntum/support/issues/10540, can you still reproduce it in the latest 6.2 version?

Post by ghulam.ghous »

Hey there,

Regarding https://github.com/bryntum/support/issues/10539, this isn’t a bug but a configuration issue. You have passed the subGridConfigs prop directly to the BryntumGanttWrapper, which we don’t recommend. For props that won’t change at runtime, use static configuration; for props that must change dynamically, manage them with React’s useState hook.

So you had this code:

const Gantt = () => {

    return (
            <BryntumGantt subGridConfigs={{ locked: { 'flex': 3 }, normal: { 'flex': 4 } }} />
    );
};

Instead, it should be:

const Gantt = () => {

    const [subGridConfigs, setSubGridConfigs] = React.useState({ 
               locked: { 'flex': 3 }, 
               normal: { 'flex': 4 } 
    });

    return (
            <BryntumGantt subGridConfigs={subGridConfigs} />
    );
};

We outline this best practice in our guide:
https://bryntum.com/products/gantt/docs/guide/Gantt/integration/react/guide#best-practices

Switching to the useState approach resolved the issue. Here is the updated demo and video clip showing it in working:

Screen Recording 2025-04-29 at 9.32.51 PM.mov
(25.65 MiB) Downloaded 6 times
Drawer-Locked Issue.zip
(1.57 MiB) Downloaded 3 times
Post Reply