Skip to content

Conversation

@catalinaperalta
Copy link
Member

@catalinaperalta catalinaperalta commented Oct 3, 2025

Adding some tests for scenarios that folks frequently customize in their client libraries. Eventually, client libraries should be able to customize LRO generation based on typespec definitions like custom lro status values.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 3, 2025

Open in StackBlitz

npm i https://pkg.pr.new/Azure/typespec-azure/@azure-tools/azure-http-specs@3363

commit: b5b56ec

@azure-sdk
Copy link
Collaborator

azure-sdk commented Oct 3, 2025

All changed packages have been documented.

  • @azure-tools/azure-http-specs
Show changes

@azure-tools/azure-http-specs - internal ✏️

Adding lro tests

@azure-sdk
Copy link
Collaborator

azure-sdk commented Oct 3, 2025

You can try these changes here

🛝 Playground 🌐 Website

Copy link
Contributor

@iscai-msft iscai-msft left a comment

Choose a reason for hiding this comment

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

This overall looks pretty good to me, however I would reorganize. I would put all of these into one folder and main.tsp, call it azure-core/lro/lro-status, and have a namespace for cancelled, failed etc

let uploadPollCount = 0;

function uploadPendingHandler(req: MockRequest) {
req.expect.containsQueryParam("api-version", "2022-12-01-preview");
Copy link
Contributor

Choose a reason for hiding this comment

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

depending on whether we really want to test api version, we either should remove it from this file, or explicitly state in the scenario docs that we're looking for api version of a certain value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants