-
Notifications
You must be signed in to change notification settings - Fork 3.5k
/api/layout does not expose edge confidence #2130
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestparsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edgespriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.ux/behaviorDisplay bugs, docs, adoption UXDisplay bugs, docs, adoption UX
Description
Activity
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestparsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edgespriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.ux/behaviorDisplay bugs, docs, adoption UXDisplay bugs, docs, adoption UX
Severity: medium.
CALLSedges carryconfidence,strategy,candidates,viaviaquery_graph,but the layout endpoint returns only
{source, target, type}— 0 of ~208 000 edgescarry confidence. The graph UI therefore cannot distinguish an LSP-resolved call
from a
suffix_matchguess, and neither can any HTTP consumer.Ask: include
confidenceandstrategyon layout edges, ideally with amin_confidencequery parameter.Observed on v0.10.8 (build
996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.