Skip to content

docs: 在阶段 C 冻结 graph 表生成 API、索引与校验规范 #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0x5143 merged 2 commits into from
Jul 7, 2026
Merged

docs: 在阶段 C 冻结 graph 表生成 API、索引与校验规范 #47

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e7f89a
docs: add graph spec freeze issue
0x5143 Jul 7, 2026
13a1e26
Merge branch 'master' into 2lezo4-codex/-graph-issue
0x5143 Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 34 additions & 1 deletion docs/optimization-plan-2026-07.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,40 @@ DataTableManagerExtension.Register();

- 设计文档明确格式、生成代码形态、运行时查询 API。

#### C4. 确认 tree 表生成 API、索引约束与数据校验规则
#### C4. 冻结 `graph` 表生成 API、索引约束与校验规范

背景设计参考：`docs/graph-table-design.md`。在进入实现前，需要先冻结 `graph` 表的生成 API、索引约束与校验规范，避免 parser、validator、template 与文档在后续实现中各自演进。

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update graph freeze task to match implemented status

The referenced design doc already says graph is implemented and lists GraphTableParser/the graph template as added (docs/graph-table-design.md lines 3 and 126-130), so adding this as work to freeze "before implementation" makes the phase plan stale as soon as it is introduced. In this context, readers following the plan would treat completed parser/template/validation work as not started; please reword this as reconciling or validating the existing graph implementation and its remaining policy gaps.

Useful? React with 👍 / 👎.


需要确认的生成 API：

- 节点集合查询。
- 出边、入边、关联边查询。
- 前驱、后继、邻居查询。
- 两点边查询。
- `HasEdge` / `HasPath`。
- `FindPath`。
- BFS 遍历。
- `TryGetEdge` / edge id 查询。

需要确认的索引约束：

- `EdgeId` 为内建唯一索引。
- `From` / `To` 为分组索引。
- 节点集合是否始终由 `From` / `To` 自动推导。

需要确认的校验规则：

- `EdgeId`、`From`、`To` 不能为空。
- `EdgeId` 不能重复。
- `Weight` 字段如存在必须可解析为数字。
- 是否允许自环、重边、孤立节点、无向图语义。

**验收标准：**

- API 命名和返回类型在实现前冻结。
- 文档、parser、validator、template 的行为一致。
- 后续实现不得在 `DataTableProcessor` 主流程中继续追加 graph 专用分支。
#### C5. 确认 tree 表生成 API、索引约束与数据校验规则

背景设计参考：`docs/tree-table-design.md`。

Expand Down
Loading