[Bug] ganttInstance.setRecords后，甘特图起止时间异常
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 486
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 16
Description
Version
1.22.2
Link to Minimal Reproduction
参照下面的示意图
Steps to Reproduce
tableInstance.addRecord(records, recordIndex);
ganttInstance.setRecords(tableInstance.records);
Current Behavior
甘特图添加任务(task)后，树形表格的上级未更新起止时间，甘特图的任务条也无法突破初始化时的最小时间和最大时间区间，详见下图
Expected Behavior
- 添加任务后，能自动更新树形表格上层的起止时间；（如有其他方法能达到此目的，烦请告知）
- 甘特图重新setRecords后，所有任务条的起止日期能正常显示
Environment
- OS: WIN10
- Browser: Edge最新版、Chrome最新版
- Framework: 无
Any additional comments?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with tableInstance.addRecord(records, recordIndex) followed by ganttInstance.setRecords(tableInstance.records), using the referenced screenshot for comparison. Investigate how parent start/end times and task-bar date bounds are recalculated after setRecords; done means parent ranges update and all task bars display dates beyond the initial minimum and maximum.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100