Dependencies module (FS/SS/FF/SF)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Read parent issue #25 and the module API work in issue #28 first; this issue is blocked by #28. Then inspect CalendarCore and the existing write pipeline to understand where dependency handling belongs. Done means the module meets the listed creation, cycle validation, cascading, validation, and tree-shaking criteria.
Written by the indexing model from the issue text.
Description
Parent
https://github.com/TanStack/time/issues/25
What to build
Extract the FS/SS/FF/SF event dependency system into a proper module. When registered, the module adds dependency-aware transformation to the write pipeline: moving a predecessor event automatically cascades the required shift to all dependents in topological order.
This module is the reason the Timeline/Gantt view exists as a product. Extracting it from `CalendarCore` into a module also fixes the current architecture where Gantt semantics are baked into the Calendar kernel.
Acceptance criteria
- `DependenciesModule` plugs into the kernel via the module API (#28)
- `createDependency(sourceId, targetId, type)` creates a link and validates it does not form a cycle
- Moving a predecessor cascades the correct shift to all dependents (FS: finish-to-start, SS: start-to-start, FF: finish-to-finish, SF: start-to-finish)
- Cascade propagates transitively through the dependency graph in topological order
- `validateEventDependencies()` checks whether placing an event satisfies its predecessor constraints
- Circular dependency detection rejects the link with a descriptive error before it is committed
- Removing the `DependenciesModule` causes dependency code to tree-shake out of the bundle
Blocked by
- Dominant language
- TypeScript
- Stars
- 621
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from TanStack/time
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 5/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 32/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxc-project/tsrs#1010 ·
Maintainers usually reply within 1 day
-
area:infra area:storage bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
THU-MAIC/OpenMAIC#2311 · 1 comment ·
Maintainers usually reply within 1 day
-
docs documentation need-triage SaaS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement from-app needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nightly-labs/openbot#10973 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30328 · 1 comment ·
Maintainers usually reply within 1 day