Vihren Atlas

extHostMcp.ts ×5

Code frontier

unlabeled · c_132753315816

18 tests · 83593 LOC · 310 files · introduces 0 tests · 25 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
5 ranges25 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
5920 ranges83593 lines · 310 files · Browse complete extent
All tests (intent)
18 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: 25 introduced LOC across 5 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

src/vs/workbench/api/common/extHostMcp.ts 25 introduced LOC · 5 ranges

Open complete file

1089 fetch: (url, init) => fetch(url, init as MinimalRequestInit)
1090 });
1091 > for (const err of errors) { extHostMcp.ts
1092 log(LogLevel.Warning, `Error fetching resource metadata: ${err}`);
1093 }
1094 > log(LogLevel.Info, `Discovered resource metadata at ${discoveryUrl}`); extHostMcp.ts
1095 >
1096 > // Determine if resource metadata came from header or well-known
1097 resourceMetadataSource = resourceMetadataChallenge ? IAuthResourceMetadataSource.Header : IAuthResourceMetadataSource.WellKnown;
1098
1102 if (!serverMetadataUrl) {
1103 log(LogLevel.Warning, `No authorization_servers found in resource metadata ${discoveryUrl} - Is this resource metadata configured correctly?`);
1104 > } else { extHostMcp.ts
1105 > log(LogLevel.Info, `Using auth server metadata url: ${serverMetadataUrl}`);
1106 > serverMetadataSource = IAuthServerMetadataSource.ResourceMetadata;
1107 > }
1108 > scopesChallenge ??= metadata.scopes_supported;
1109 > resource = metadata;
1110 } catch (e) {
1111 log(LogLevel.Warning, `Could not fetch resource metadata: ${String(e)}`);
1131 fetch: (url, init) => fetch(url, init as MinimalRequestInit)
1132 });
1133 > for (const err of errors) { extHostMcp.ts
1134 log(LogLevel.Warning, `Error fetching authorization server metadata: ${err}`);
1135 }
1136 > log(LogLevel.Info, `Discovered authorization server metadata at ${discoveryUrl}`); extHostMcp.ts
1137 >
1138 > // If serverMetadataSource is not yet defined, it means we fell back to baseUrl
1139 > // and successfully fetched from well-known
1140 > serverMetadataSource ??= IAuthServerMetadataSource.WellKnown;
1141 >
1142 > return new AuthMetadata(
1143 > URI.parse(serverMetadataUrl),
1144 > metadata,
1145 > resource,
1146 > scopesChallenge,
1147 > { resourceMetadataSource, serverMetadataSource },
1148 > log
1149 > );
1150 } catch (e) {
1151 log(LogLevel.Warning, `Error populating auth server metadata for ${serverMetadataUrl}: ${String(e)}`);

Direct hierarchy

Parents

Children