Severity: medium — partly a docs issue.
linked_projects is [] for every freshly indexed project, which reads as "no
cross-repo links exist" rather than "this mode has not been run". When run, the
documented wildcard fails:
target_projects: ["*"] → "cross-repo source or target project is missing, invalid, or not indexed"
target_projects: ["proj_a","proj_b"] → works
The tool description states Use ["*"] for all indexed projects.
Separately, the matches it produced were low-value: a frontend's client-side
router paths (e.g. /dashboard in a React route table) were matched against
backend Route nodes, while the actual REST calls the frontend makes were not
matched at all.
Ask: fix or document the wildcard; distinguish client-side route strings from
HTTP call sites when matching.
Observed on v0.10.8 (build 996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.
Severity: medium — partly a docs issue.
linked_projectsis[]for every freshly indexed project, which reads as "nocross-repo links exist" rather than "this mode has not been run". When run, the
documented wildcard fails:
The tool description states
Use ["*"] for all indexed projects.Separately, the matches it produced were low-value: a frontend's client-side
router paths (e.g.
/dashboardin a React route table) were matched againstbackend
Routenodes, while the actual REST calls the frontend makes were notmatched at all.
Ask: fix or document the wildcard; distinguish client-side route strings from
HTTP call sites when matching.
Observed on v0.10.8 (build
996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.