[nicolejms]

Summary

Match explicit lists of built-in resource types in AppGraph:

• Containers: Applications.Core/containers and Radius.Compute/containers.
• Gateways: Applications.Core/gateways and Radius.Compute/routes. Radius.Compute/routes replaces gateways for ingress.

Type matching ignores letter case. User-defined types with the same names (for example Contoso.Net/gateways) get no special handling. This PR keeps support for the legacy types. It does not remove legacy resources or migrate the saved graph records.

Reason for change

AppGraph compared resource types with the literal strings Applications.Core/containers and Applications.Core/gateways. Resources of the new built-in types thus used the wrong initial layout row, and route edges did not get the direction correction.

Issue #373 names Radius.Core/containers and Radius.Core/gateways. The Radius manifest deploy/manifest/built-in-providers/self-hosted/radius_core.yaml defines no such types. Radius.Core defines only environments, applications, recipePacks, terraformSettings, and bicepSettings. The real new types are Radius.Compute/containers (containers.yaml) and Radius.Compute/routes (routes.yaml). The graph API reports a route-to-container link as an Outbound dependency edge on the route and an Inbound copy on the container (pkg/graph/edges/edges.go). This is the same shape as legacy gateway edges, so the same direction correction applies.

Fixes #373

How to test

Use Node.js 24 and the Yarn version set in package.json. Run corepack yarn install --immutable. If the browser is not installed, run corepack yarn playwright install chromium. For browser commands below, set PLAYWRIGHT_BROWSER_CHANNEL=chromium (PowerShell: $env:PLAYWRIGHT_BROWSER_CHANNEL='chromium'). The app and Storybook test commands start and stop their own servers; no Radius cluster is needed.

1. Run corepack yarn test --watchAll=false --runInBand --coverage=false packages/rad-components/src. Both type sets must place containers without inbound connections in the leading row. Gateway and route edges must point to the container before and after layout. User-defined */gateways, */routes, and */containers types (for example Contoso.Net/gateways and Radius.Networking/gateways) must not get the special handling.
2. Run corepack yarn test:e2e packages/app/e2e-tests/radiusGraph.test.ts --workers=1. Open each application from the list. The Radius.Core application's graph mock returns Radius.Compute/containers, Radius.Compute/routes, and Radius.Data/redisCaches resources. Both graphs must show the gateway or route edge to frontend, not the reverse edge.
3. Run corepack yarn test:e2e:components --workers=1. The real renderer must retain its nodes, edges, controls, and layout behavior.

Validation results (commit 2):

Command	Result
corepack yarn test ... AppGraph.test.tsx graphInvariants.test.ts before the fix	Failed as expected: 7 new tests failed (route direction, route topology, user-defined types, letter case); 114 passed. Tests were changed before the code.
corepack yarn test --watchAll=false --runInBand --coverage=false packages/rad-components/src after the fix	Passed: 161 tests in 5 suites, including graphRecords.test.ts (saved records unchanged).
corepack yarn test:e2e packages/app/e2e-tests/radiusGraph.test.ts --workers=1 after the fix	Passed: 5 tests with Chromium.
Same E2E-03 test with the previous endsWith code	Failed as expected on the Radius.Compute graph.
corepack yarn test:e2e:components --workers=1	Passed: 8 tests in 3 runs in a row. The first run had 1 timing failure in GU-11 (scheduled-work check), which this PR does not touch.
corepack yarn tsc	Passed.
corepack yarn lint:all	Passed.
corepack yarn prettier --write on the changed files	No changes after formatting.
shellcheck .devcontainer/postcreate.sh	Passed. No shell files changed.
git diff --check	Passed.

File change summary

File	Summary of change
packages/rad-components/src/components/appgraph/AppGraph.tsx	Match explicit lists of built-in container and gateway or route types, without regard to letter case.
packages/rad-components/src/components/appgraph/__test__/AppGraph.test.tsx	Add unit cases for both type sets, negative cases for user-defined types such as Contoso.Net and Radius.Networking, and a letter-case case.
packages/rad-components/src/__test__/graphInvariants.test.ts	Check gateway and route topology through the real model builder and layout.
packages/app/e2e-tests/radiusGraph.test.ts	Return Radius.Compute and Radius.Data types for the Radius.Core application, and check the exact visible edge direction.
docs/design/2026-09-dashboard-plugin-test-plan.md	Record the #373 fix, the real type names, and the coverage; remove #373 from the known-defects table; keep corpus migration separate.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[nicolejms]

Playwright screenshots for #373. All 13 tests passed: 5 app graph tests and 8 component tests. These images use mocked API data, not a live Radius deployment. The images show the Radius.Core application graph, a close-up of the Radius.Core/containers label, and the legacy graph for comparison.

[nicolejms]

Updated screenshots: real Radius.Compute types

These screenshots replace the earlier ones, which showed Radius.Core/containers. Radius does not define that type. The Radius.Core application's graph now uses Radius.Compute/containers, Radius.Compute/routes, and Radius.Data/redisCaches. Playwright E2E-03 captured them with mocked API data, not a live cluster.

Radius.Core application graph

The route edge points to frontend, the same direction as the legacy gateway.

Route and container close-ups

Legacy Applications.Core graph (no change)

[nithyatsu]

Fix looks correct and the coverage across both type sets is good. One doc fix needed before merge, plus a nit.