Vihren Atlas

reducer.ts ×5

Code frontier

unlabeled · c_047960806046

35 tests · 11531 LOC · 50 files · introduces 0 tests · 17 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
5 ranges17 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
729 ranges11531 lines · 50 files · Browse complete extent
All tests (intent)
35 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.

1 file ranked by introduced lines: 17 introduced LOC across 5 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

src/vs/platform/agentHost/common/state/protocol/channels-chat/reducer.ts 17 introduced LOC · 5 ranges

Open complete file

496 case ActionType.ChatToolCallComplete:
497 return refreshSummaryStatus(updateToolCallInParts(state, action.turnId, action.toolCallId, tc => {
498 > if (tc.status !== ToolCallStatus.Running && tc.status !== ToolCallStatus.PendingConfirmation && tc.status !== ToolCallStatus.AuthRequired) { reducer.ts
499 return tc;
500 }
508 // challenge (`chat/toolCallAuthResolved`) before completing
509 // successfully.
510 > if (tc.status === ToolCallStatus.AuthRequired && action.result.success) { reducer.ts
511 return tc;
512 }
515 ? tc.confirmed
516 : ToolCallConfirmationReason.NotNeeded;
517 > const selectedOption = tc.status === ToolCallStatus.Running || tc.status === ToolCallStatus.AuthRequired reducer.ts
518 ? tc.selectedOption
519 : undefined;
520 > // Preserve any partial content produced before the call paused for reducer.ts
521 > // auth — a client cancelling from `auth-required` without
522 > // authenticating never resumes execution, so this is the only
523 > // content the tool ever produced unless `action.result` overrides it.
524 > const preAuthContent = tc.status === ToolCallStatus.AuthRequired ? tc.content : undefined;
525 > // Cancelling from `auth-required` always completes terminally: the
526 > // pending auth challenge isn't a "pending result" the client can
527 > // review, so `requiresResultConfirmation` is ignored for this path —
528 > // it must never enter `pending-result-confirmation`.
529 > if (action.requiresResultConfirmation && tc.status !== ToolCallStatus.AuthRequired) {
530 return {
531 status: ToolCallStatus.PendingResultConfirmation,
545 toolInput: tc.toolInput,
546 confirmed,
547 > ...(selectedOption ? { selectedOption } : {}), reducer.ts
548 > ...(preAuthContent ? { content: preAuthContent } : {}),
549 > ...action.result,
550 > };
551 }));
552

Direct hierarchy

Parents

Children