strange behavior with timeRanges about svelte-gantt

[nitish-darji]

Hello,

I'm facing same issue when change view and have more than one timeRanges then only first timeRange object updated.

Also I've try gantt.refreshTimeRanges(); but not success.

Just reference below function call internal from lib

     function refreshTimeRanges() {
	timeRangeStore._update(({ ids, entities }) => {
		ids.forEach(id => {
			const timeRange = entities[id];
			const newLeft = columnService.getPositionByDate(timeRange.model.from) | 0;
			const newRight = columnService.getPositionByDate(timeRange.model.to) | 0;
			timeRange.left = newLeft;
			timeRange.width = newRight - newLeft;
		});
		return { ids, entities };
	});
}

Please help me out any workaround.

Thanks in advance.

[ANovokmet]

Interesting, I've just tried the demo with multiple time ranges and I did not experience any issues. Any chance you share the rest of your gantt configuration?

[ANovokmet]

Were there any errors in the console? I've fixed an error when time ranges get destroyed which could result in a stuck view.

[nitish-darji]

thanks @ANovokmet for quick reply

I'm working on angular and [email protected] version

please check below attached demo link
https://stackblitz.com/edit/angular-fj36mp

after upgrade latest version now it's working as expected (except one issue when build project then one error occur as below)
node_modules/svelte-gantt/types/modules/table/tableHeader.d.ts:1:27

investigate error then found node_modules/svelte-gantt/types/modules/table/tableHeader.d.ts file import { SvelteRow } from "src/core/row"; when I replace with import { SvelteRow } from "../../core/row"; then it's working fine

Again thanks @ANovokmet

[ANovokmet]

@nitish-darji thanks for the heads up on this error, I'll be investigating it.

[V-Py]

Hello @nitish-darji, do you still experience this issue cause after some tests I can't reproduce it either with the current version ?
Thanks in advance :)

[V-Py]

No answer and not able to reproduce the bug described