bvandeusen/FabledGrimoire
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 53 Wiki Activity

dev → main: a name defined in two packages counts only in the canon's own (#6495) #219

Merged
bvandeusen merged 1 commits from dev into main 2026-10-26 22:26:20 -04:00
Conversation 0 Commits 1 Files Changed 2
+77 -22
1 Commits
Author SHA1 Message Date
bvandeusenandClaude Opus 5.5 b87178d261 fix(6495): a name defined in two packages counts only in the canon's own
CI & Build / Python lint (push) Successful in 2s
Details
CI & Build / Plugin hooks (push) Successful in 14s
Details
CI & Build / integration (push) Successful in 1m22s
Details
CI & Build / TypeScript typecheck (push) Successful in 37s
Details
CI & Build / Python tests (push) Successful in 1m59s
Details
CI & Build / Build & push image (push) Successful in 43s
Details 
A by-name reference edge could not tell two definitions of one name apart:
in a Go repo that defines `file` as importRun.file (internal/files, the
canon) and as sftpRun.file (internal/replication), a mirror test calling
`m.file(` was recorded as a use of the canon.

names_canon now takes defined_at, every repo path that defines each name,
in place of the shape file's own names. The own-file rule is unchanged.
When the repo also defines the canon's name somewhere the canon is not
recorded, a mention counts only from the canon's own package: the
directory of a file location exactly, or under a directory location.
A name defined once resolves as before. Proposer version 8 -> 9, so the
next coverage refresh re-reads every row and replaces its reference edges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-26 20:05:09 -04:00