Files
taskgraph_ts/tasks/implementation/graph/construction.md
glm-5.1 8d384a7b3e feat(graph/construction): implement TaskGraph construction methods
- fromTasks: bulk import via serialized blob, orphan nodes for dangling refs,
  DuplicateNodeError for duplicates, edge dedup, null→undefined stripping
- fromRecords: strict validation (TaskNotFoundError for dangling refs,
  DuplicateEdgeError for duplicate edges), per-edge qualityRetention
- fromJSON: TypeBox Value.Check validation, InvalidInputError on schema failure,
  orphan nodes preserved
- addTask: throws DuplicateNodeError if ID exists
- addDependency: throws TaskNotFoundError/DuplicateEdgeError, deterministic
  edge keys per ADR-006, default qualityRetention 0.9
- taskInputToNodeAttrs: strips null→undefined for categorical fields,
  drops non-graph fields (tags, assignee, due, created, modified)
- 47 new unit tests (304 total, all passing)
2026-04-27 11:59:56 +00:00

71 lines
4.4 KiB
Markdown

---
id: graph/construction
name: Implement TaskGraph construction methods (fromTasks, fromRecords, fromJSON, addTask, addDependency)
status: completed
depends_on:
- graph/taskgraph-class
scope: broad
risk: high
impact: phase
level: implementation
---
## Description
Implement the four construction methods in `src/graph/construction.ts` and integrate them as static methods on `TaskGraph`. These are the primary ways to create a graph instance from structured data. Each method has distinct semantics for edge handling, error behavior, and validation.
Per [graph-model.md](../../../docs/architecture/graph-model.md), the preferred internal approach is to build a serialized graph JSON blob and call `graph.import()` for paths 1 and 2 (better performance than N individual addNode/addEdge calls).
## Acceptance Criteria
- [x] `TaskGraph.fromTasks(tasks: TaskInput[]): TaskGraph`:
- Transforms `TaskInput[]` into node data + edge data, builds serialized blob, calls `graph.import()`
- Each `dependsOn` entry creates an edge with default `qualityRetention: 0.9`
- `dependsOn` targets not matching any task ID become orphan nodes with default attributes
- Duplicate task IDs throw `DuplicateNodeError`
- Uses `mergeNode` for idempotent node merging (same ID gets merged attributes)
- Duplicate `dependsOn` entries for the same pair create only one edge (idempotent via `addEdgeWithKey`)
- [x] `TaskGraph.fromRecords(tasks: TaskInput[], edges: DependencyEdge[]): TaskGraph`:
- Edges must reference tasks that exist in the `tasks` array — throws `TaskNotFoundError` for dangling references
- Per-edge `qualityRetention` from the `DependencyEdge` objects
- Duplicate task IDs throw `DuplicateNodeError`
- Duplicate edges (same prerequisite→dependent pair) throw `DuplicateEdgeError`
- [x] `TaskGraph.fromJSON(data: TaskGraphSerialized): TaskGraph`:
- Validates input against `TaskGraphSerialized` schema (using TypeBox `Value.Check`)
- Uses `graph.import()` on the validated data
- Orphan nodes in JSON are preserved
- [x] `addTask(id: string, attributes: TaskGraphNodeAttributes): void`:
- Throws `DuplicateNodeError` if ID already exists
- Adds node to internal graphology instance
- [x] `addDependency(prerequisite: string, dependent: string, qualityRetention?: number): void`:
- Throws `TaskNotFoundError` if either endpoint doesn't exist
- Throws `DuplicateEdgeError` if edge already exists
- Uses `addEdgeWithKey` with deterministic key `${prerequisite}->${dependent}`
- Default `qualityRetention: 0.9` if not provided
- [x] `fromTasks`/`fromRecords` strip `null``undefined` for categorical fields during `TaskInput``TaskGraphNodeAttributes` transformation
- [x] `TaskInput` fields `tags`, `assignee`, `due`, `created`, `modified` are not stored on graph nodes (belong to caller)
- [x] Unit tests for each construction method: happy path, error cases, edge cases (empty arrays, cycles not rejected at construction time)
- [x] All construction methods use deterministic edge keys per ADR-006
## References
- docs/architecture/graph-model.md — construction paths, TaskInput→attributes transformation, error handling table
- docs/architecture/api-surface.md — TaskGraph class, fromTasks/fromRecords/fromJSON/addTask/addDependency
- docs/architecture/decisions/006-deterministic-edge-keys.md — deterministic edge keys
## Notes
Implementation approach:
- `fromTasks` and `fromRecords` use the bulk `graph.import()` approach per architecture recommendation (build serialized blob, import in one call).
- `fromJSON` adds TypeBox `Value.Check()` validation before importing, throwing `InvalidInputError` for schema violations.
- `fromTasks` creates orphan nodes for dangling dependsOn references with default attributes `{ name: <dep-id> }`.
- `fromRecords` is strict — any dangling edge reference throws `TaskNotFoundError`.
- `addTask` and `addDependency` are thin wrappers with validation on the underlying graphology instance.
- The `taskInputToNodeAttrs` helper strips null→undefined for categorical fields and drops non-graph fields (tags, assignee, due, created, modified).
## Summary
Implemented all five construction methods on the TaskGraph class.
- Modified: `src/graph/construction.ts` (full implementation of fromTasks, fromRecords, fromJSON with validation, addTask, addDependency; taskInputToNodeAttrs helper)
- Modified: `test/graph.test.ts` (added 47 new tests for construction methods, preserved 42 existing tests)
- Tests: 304 total (all passing), lint clean