solidjs / solid / 36071296300

74%

main: 89%

push

github

fix(web): performance-tracks labels start at the nearest component (#3645)

Track labels in the Performance panel now begin at the nearest component
the developer wrote (`<Search> › results`) rather than the full runtime
path from `<Document>`. Chrome elides the middle of long labels, which
hid exactly the segment naming the owning component. Solid's own flow
controls (Show, For, Repeat, Switch, Match, Errored, Loading, Reveal,
Portal, Dynamic) are not anchors, so `<Card> › <Show> › effect` stays.
The full path remains as the `Owner path` property, now also set on
flight, fallback and server-boundary spans when the label was cut.

Applied at every label site: rerun/create/effect-callback spans,
Propagation `← cause` labels, diagnostic markers, Async fallback, and
Server-track `solid-boundary` spans (wire `desc` unchanged).

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

606 of 894 branches covered (67.79%)

Branch coverage included in aggregate %.

883 of 1142 relevant lines covered (77.32%)

25.28 hits per line