Repository navigation
Enable Azure C# emitters in the website playground - #6060
Merged
Timothee Guerin (timotheeguerin) merged 2 commits intoNov 11, 2026
Merged
Timothee Guerin (timotheeguerin) merged 2 commits into
Timothee Guerin (timotheeguerin) merged 2 commits into
Conversation
Contributor
|
No changes needing a change description found. |
Contributor
|
You can try these changes here
|
JoshLove-msft
approved these changes
Nov 11, 2026
Timothee Guerin (timotheeguerin)
marked this pull request as ready for review
November 11, 2026 18:01
Timothee Guerin (timotheeguerin)
requested review from
Mark Cowlishaw (markcowl) and
Jeff Fisher (xirzec)
as code owners
November 11, 2026 18:01
Timothee Guerin (timotheeguerin)
deleted the
feat/azure-csharp-website-playground
branch
November 11, 2026 18:58
Mark Cowlishaw (markcowl)
pushed a commit
to markcowl/typespec-azure
that referenced
this pull request
Nov 12, 2026
Adds the unbranded `@typespec/http-client-csharp` emitter to the Azure website playground's additional packages, following up on Azure#6060. Like the Azure C# emitters, its import map is loaded only for the latest compiler version. It is listed last so it appears at the bottom of the emitter dropdown; all of these packages map the shared `@typespec/http-client` peer to the same version (0.17.0). ### Validation Tested in a browser against a local website on `http://localhost:3000`: - Both the unbranded and Azure C# emitters generate clients, and the unbranded output contains no Azure references. - Historical versions (`0.73.x`) do not show the additional C# emitters. - If the unbranded import map is missing, the playground and the Azure emitter still work. Note: the C# generation server's CORS allowlist does not include the default dev origin `127.0.0.1:4321`, so local C# emission only works from an allowed origin such as `localhost:3000`. Production (`azure.github.io`) is allowed. --generated by Copilot --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
The Azure website playground cannot currently generate Azure C# clients. Load the published data-plane, management-plane, and provisioning browser import maps using the same additional-package approach as the TypeSpec website.
This is a website-only alternative to #5968: no standalone playground support, emitter npm dependencies, or Vite changes. Historical compiler selections remain unchanged, and unavailable package maps do not prevent the playground from loading.
Validated with the real published data-plane bundle and hosted generator in Chromium: a small Widget service generated 29 C# files without compiler errors. Historical-version loading also passed. Provisioning remains hidden until its browser map is published.
Relates to Azure/azure-sdk-for-net#64101.
Temporarily omit browser installation from PR-tools preview publishing to avoid the Ubuntu repository/proxy failures blocking previews. Browser installation in the E2E test jobs is unchanged.