<BryntumScheduler
ref={'scheduler'}
autoHeight={true}
startDate={new Date(2019, 1, 7, 8)}
endDate={new Date(2019, 1, 7, 18)}
eventStyle="colored"
tickSize={80}
barMargin={2}
/>
However if we add the attribute mode="vertical", things get nasty. (I'll paste a glimpse of the error code below since is pretty big).
We dig a little into your BryntumScheduler component looking for the Mode attribute, but seems like its not there, at least in the version:
/**
* @author Saki
* @date 2019-06-06 19:54:44
* @Last Modified by: Saki
* @Last Modified time: 2019-06-13 17:28:18
*/
-----
TypeError: Cannot read property 'cells' of undefined
VerticalTimeAxis.refresh
/Users/freddytorres/Development/Sportslogic/Admin/scheduler/build/scheduler.module.js:179
176 | _0x403b2f=releaseEventActions[action],_0x176325=renderEventActions[action];if(_0x403b2f&&oldConfig){const _0x209313=oldConfig[_0x29e5('0x2e0')]['tplData'],_0x5172c1={'tplData':_0x209313,'assignmentRecord':_0x209313[_0x29e5('0x143f')],'eventRecord':_0x209313[_0x29e5('0x117d')],'resourceRecord':_0x209313[_0x29e5('0x11fe')],'element':element};scheduler[_0x29e5('0x194')]('releaseEvent',_0x5172c1);}if(_0x176325){const _0x2f305a=config['elementData'][_0x29e5('0x14d9')],_0x54e3e3={'tplData':_0x2f305a,'assignmentRecord':_0x2f305a[_0x29e5('0x143f')],'eventRecord':_0x2f305a['eventRecord'],'resourceRecord':_0x2f305a[_0x29e5('0x11fe')],'element':element};element[_0x29e5('0x2e0')][_0x29e5('0x16f')]=element;_0x54e3e3[_0x29e5('0x14ec')]=action===_0x29e5('0x14ed');scheduler['trigger ....
The other error is:
TypeError: Cannot read property 'destroy' of undefined
BryntumScheduler.componentWillUnmount
src/components/scheduler/BryntumScheduler.js:153
150 |
151 | // React component removed, destroy engine
152 | componentWillUnmount() {
> 153 | this.schedulerEngine.destroy && this.schedulerEngine.destroy();
154 | }
155 |
156 | // Component about to be updated, from changing a prop using state. React to it depending on what
----
Again, this just happens if we add mode="vertical" to the snippet