Skip to content

Fix response type of putExtensibleStringValue in special-words spec - #9987

Merged
Yuchao Yan (msyyc) merged 8 commits into
mainfrom
publish/http-specs-03-11
Mar 11, 2026
Merged

Yuchao Yan (msyyc) merged 8 commits into
mainfrom
publish/http-specs-03-11

Conversation

@msyyc

@msyyc Yuchao Yan (msyyc) commented Mar 11, 2026 •

Copy link
Copy Markdown
Contributor

moved from #9953

Follow-up to #9785: the putExtensibleStringValue operation was missing an explicit response content-type header, inconsistent with the pattern used by other extensible enum endpoints.

  • Updated return type in packages/http-specs/specs/special-words/main.tsp:
putExtensibleStringValue(@body body: ExtensibleString): {
    @header contentType: "application/json";
    @body body: ExtensibleString;
};

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • telemetry.astro.build
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/typespec/typespec/website/node_modules/.bin/../astro/astro.js build sh s/.b�� ../../website/sr--llmstxt sh _modules/pnpm/dist/node-gyp-bin/node --no-emit git _modules/pnpm/digenerate-scenarios-summary node tobu�� build.json sh /.bin/sh ld.json && pnpm node pnpm tobuf/reference node (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

@pkg-pr-new

pkg-pr-new Bot commented Mar 11, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-specs@9987

commit: 39139db

@microsoft-github-policy-service microsoft-github-policy-service Bot added the lib:http-specs For issues/prs related to the @typespec/http-specs package label Mar 11, 2026
@azure-sdk

Azure SDK Bot (azure-sdk) commented Mar 11, 2026 •

Copy link
Copy Markdown
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

Comment thread packages/http-specs/specs/special-words/main.tsp Outdated

Copilot AI commented Mar 11, 2026

Copy link
Copy Markdown
Contributor

Yuchao Yan (@msyyc) I've opened a new pull request, #9992, to work on those changes. Once the pull request is ready, I'll request review from you.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@weidongxu-microsoft Weidong Xu (weidongxu-microsoft) left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unsure whether it should go patch

@microsoft-github-policy-service microsoft-github-policy-service Bot added the emitter:client:python Issue for the Python client emitter: @typespec/http-client-python label Mar 11, 2026
@msyyc
Yuchao Yan (msyyc) force-pushed the publish/http-specs-03-11 branch from 5418a9e to 9390910 Compare March 11, 2026 07:26
@msyyc Yuchao Yan (msyyc) removed the emitter:client:python Issue for the Python client emitter: @typespec/http-client-python label Mar 11, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot added the emitter:client:python Issue for the Python client emitter: @typespec/http-client-python label Mar 11, 2026
@msyyc
Yuchao Yan (msyyc) force-pushed the publish/http-specs-03-11 branch from 9390910 to b75cc49 Compare March 11, 2026 07:28
@msyyc
Yuchao Yan (msyyc) added this pull request to the merge queue Mar 11, 2026
Merged via the queue into main with commit 8b11cfc Mar 11, 2026
38 checks passed
@msyyc
Yuchao Yan (msyyc) deleted the publish/http-specs-03-11 branch March 11, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:python Issue for the Python client emitter: @typespec/http-client-python lib:http-specs For issues/prs related to the @typespec/http-specs package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants