Repository navigation
Remove the Electron Playground - #1546
Merged
Merged
Conversation
This PR deletes tests/playground, the Electron app for trying MXC policies interactively. Since #1355 it has called SDK entry points that no longer exist, including the empty root export, spawnSandbox, createConfigFromPolicy and spawnSandboxFromConfig. No pipeline built it, so the breakage went unnoticed. Details * Delete all 13 tracked Playground files, including its npm lockfile. * Drop the Playground lockfile from the CONTRIBUTING lockfile list. Tests * git grep -i playground finds no remaining references. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ce647283-a4dd-44d4-995a-3e0ac8f5d574 Generated-with: claude-opus-5.5
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The retirement is self-contained, with no identified blocking defects or impact on supported SDKs and CI inputs.
No open issues 🎉
What changed in this PR
Removes the obsolete Electron Playground without changing supported MXC SDKs or backend behavior.
Changes:
- Deletes the Playground application, build configuration, and supporting documentation.
- Removes its lockfile entry from contributor guidance.
| File | Description |
|---|---|
| tests/playground/tsconfig.renderer.json | Removes renderer compiler configuration. |
| tests/playground/tsconfig.main.json | Removes main-process compiler configuration. |
| tests/playground/test-scripts/winhttp-proxy-test.ps1 | Removes Playground proxy test script. |
| tests/playground/src/renderer/styles.css | Removes application styles. |
| tests/playground/src/renderer/index.html | Removes application interface. |
| tests/playground/src/renderer/app.ts | Removes interactive scenarios and controls. |
| tests/playground/src/main/preload.ts | Removes renderer communication bridge. |
| tests/playground/src/main/main.ts | Removes Electron startup and SDK integration. |
| tests/playground/playground-limitations.md | Removes obsolete compatibility documentation. |
| tests/playground/package.json | Removes application dependencies and packaging configuration. |
| tests/playground/build-renderer.js | Removes static asset build script. |
| tests/playground/.gitignore | Removes application-specific ignore rules. |
| CONTRIBUTING.md | Removes the Playground lockfile listing. |
Review effort: Balanced
Branden Bonaby (bbonaby)
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR deletes
tests/playground, the Electron app for trying MXC policies interactively. Since #1355 it has called Node SDK entry points that no longer exist: the now-empty@microsoft/mxc-sdkroot export (getPlatformSupport),spawnSandbox,createConfigFromPolicy, the pre-namespace policy getters andspawnSandboxFromConfig. No pipeline builds it, so the breakage went unnoticed. Porting it to v1 would also mean redesigning its raw-config and "Advanced" modes, because v1 accepts only a typedContainerRequest, not a raw versionedContainerConfig.Details
CONTRIBUTING.md.🔗 References
helper.tsand stalespawnSandboxFromConfigdocs.Tests
git grep -i playgroundreturned no matches after the change.tests/playground; no pipeline, workflow or script change was needed.Microsoft Reviewers: Open in CodeFlow