Reuse trace endpoint context in details
Why: Object details render the same relationship row and must identify the endpoint relative to that object. Evidence: Type checking identified the missing selected-object context after the endpoint fix. Impact: Relationship rendering is consistent in the trace view and object details. Refs: rdm-two-trees-latest-templates
This commit is contained in:
@@ -668,7 +668,7 @@ function ObjectDetailView({ detail }: { detail: ObjectDetail }) {
|
||||
{detail.relations && detail.relations.length > 0 && (
|
||||
<div>
|
||||
<SectionLabel>一跳关系({detail.relations.length})</SectionLabel>
|
||||
{detail.relations.map((r, i) => <RelationRow key={i} r={r} />)}
|
||||
{detail.relations.map((r, i) => <RelationRow key={i} r={r} selected={{ kind: detail.kind, id: detail.id }} />)}
|
||||
</div>
|
||||
)}
|
||||
{detail.recentEvents && detail.recentEvents.length > 0 && (
|
||||
|
||||
Reference in New Issue
Block a user