Vihren Atlas

link_util.go ×1

Code frontier

unlabeled · c_9b83e7490424

27 tests · 6641 LOC · 215 files · introduces 0 tests · 24 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges24 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
1328 ranges6641 lines · 215 files · Browse complete extent
All tests (intent)
27 testsBrowse complete intent

Neighbourhood graph

The orange circle is the focus. Violet and green circles are every ancestor and descendant, broader and narrower, at any distance; blue squares and pink diamonds are the introduced files and exact introduced tests of every visible concept, not only the focus's. Arrows point from broader to narrower concepts and bridge only concepts omitted from this view. Undirected links show source or test introduction. Concept and file size follows LOC; exact test nodes use test-count units.

Introduced files, introduced tests, and structurally relevant concept specialization

In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the native relationship evidence on this page.

Graph controls are ready.

Interactive rendering requires JavaScript and WebGL. Use the native relationship evidence on this page while the interactive map is unavailable.

Native relationship evidence

Every exact file and test below is linked only from the concept that introduces it.

Introduced tests

Every collected test enters the hierarchy at exactly one concept.

No tests are introduced at this concept. Its intent tests are introduced by other concepts.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

2 files ranked by introduced lines: 24 introduced LOC across 2 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/api/link_util.go 17 introduced LOC · 1 range

Open complete file

10 // Use this for backlinks to workflow start: the started event is always EventId=1 (FirstEventID)
11 // and is never buffered, so a concrete EventReference is appropriate.
12 > func GenerateStartedEventRefLink(namespace, workflowID, runID string) *commonpb.Link { link_util.go
13 > return &commonpb.Link{
14 > Variant: &commonpb.Link_WorkflowEvent_{
15 > WorkflowEvent: &commonpb.Link_WorkflowEvent{
16 > Namespace: namespace,
17 > WorkflowId: workflowID,
18 > RunId: runID,
19 > Reference: &commonpb.Link_WorkflowEvent_EventRef{
20 > EventRef: &commonpb.Link_WorkflowEvent_EventReference{
21 > EventId: common.FirstEventID,
22 > EventType: enumspb.EVENT_TYPE_WORKFLOW_EXECUTION_STARTED,
23 > },
24 > },
25 > },
26 > },
27 > }
28 > }
29
30 // GenerateRequestIDRefLink builds a Link with a RequestIdReference.
go.temporal.io/server/service/history/api/startworkflow/api.go 7 introduced LOC · 1 range

Open complete file

850 }
851
852 > func (s *Starter) generateStartedEventRefLink(runID string) *commonpb.Link { api.go
853 > return api.GenerateStartedEventRefLink(
854 > s.namespace.Name().String(),
855 > s.request.StartRequest.WorkflowId,
856 > runID,
857 > )
858 > }
859
860 func (s *Starter) generateRequestIdRefLink(runID string) *commonpb.Link {

Direct hierarchy

Parents

Children