Repository navigation
docs: 36 ambiguous cross-reference warnings from registry members named dict, set and type #1775
Description
Describe the bug
The docs build gives 36 "more than one target found" warnings, on both main and the merged #1103 sweep:
| Reference | Warnings |
|---|---|
dict |
21 |
type |
3 |
http |
3 |
set |
1 |
Echo |
1 |
TypeVars _AT, _BT, _DT, _IT |
the rest |
The registry members named dict, set and so on, for example pcapkit.const.reg.apptype.tcp.TCP.dict, collide with plain :obj: references. So a link meant for the builtin can resolve to an AppType member.
Expected behavior
Every reference resolves to exactly one target, and the build has no ambiguity warnings. That might come from qualifying the references, a conf.py setting, or both.
Additional context
Found by the #1103 corekit and foundation workers; a Sonnet review counted the warnings in the baseline and merged builds.
Activity
JarryShaw commentedon Oct 15, 2026
Blocked until the #1103 round-2 PRs merge. The fix qualifies cross-references across many files that those PRs are editing now, so starting earlier would conflict with them. It unblocks once
gh pr list --search "1103 in:title" --state openreturns nothing.JarryShaw commentedon Oct 15, 2026
The round-2 PRs are #1777 and #1782–#1789. Unblocks when all nine have merged.
JarryShaw commentedon Oct 15, 2026
Unblocked: all nine round-2 PRs have merged (#1777 last). A worker is on it.
docs(conf): resolve the 36 ambiguous cross-references at their source (…
docs(docs): second whole-repo pass over the non-API docs and indexes (#…