From b11e83bb65375db5ffda80d88316fee79132534a Mon Sep 17 00:00:00 2001 From: iscai-msft Date: Tue, 28 Jul 2026 15:16:28 -0400 Subject: [PATCH] Promote 14 pagination and error-handling scenarios from Backlog to Core MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit These scenarios test fundamental patterns used by shipped Azure services: Pagination (12 scenarios): - ContinuationToken (6): header/query request × body/header/nested response - Link-based (3): link, linkString, nestedLink - PageSize (2): listWithPageSize, listWithoutContinuation - XML Pagination (2): listWithContinuation, listWithNextLink Error handling (2 scenarios): - Response_StatusCodeRange_errorResponseStatusCodeInRange - Response_StatusCodeRange_errorResponseStatusCode404 Rationale: These patterns appear in real Azure services (every list operation uses pagination, every service returns errors with status code ranges). They test distinct wire-format behavior not covered by other Core scenarios, and users would file bugs if these didn't work in generated SDKs. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 421f24e7-8a8e-4dad-b066-2c4e974abd68 --- website/src/pages/can-i-use/scenario-tiers.ts | 35 +------------------ 1 file changed, 1 insertion(+), 34 deletions(-) diff --git a/website/src/pages/can-i-use/scenario-tiers.ts b/website/src/pages/can-i-use/scenario-tiers.ts index 355fb7e9a0..6dc633c426 100644 --- a/website/src/pages/can-i-use/scenario-tiers.ts +++ b/website/src/pages/can-i-use/scenario-tiers.ts @@ -60,19 +60,8 @@ export const scenarioTiers = { "Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_get", "Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_put", - // Pageable: ContinuationToken — skipped by Go, Java, JS (Python skips 1 of 6); - // custom continuation-token pagination; no ask in Azure yet (JS); - // Go tracks in https://github.com/Azure/autorest.go/issues/1494 - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderNestedResponseBody", - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseBody", - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseHeader", - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryNestedResponseBody", - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseBody", - "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseHeader", - // Pageable: AlternateInitialVerb — newly added (microsoft/typespec#9966); - // POST-based initial pagination request; no language has implemented this yet; - // fits the same pageable backlog pattern as ContinuationToken/link/PageSize + // POST-based initial pagination request; not yet broadly implemented "Payload_Pageable_ServerDrivenPagination_AlternateInitialVerb_post", // Azure AlternateType ExternalType — skipped by Go, Python, JS; @@ -95,28 +84,6 @@ export const scenarioTiers = { "Authentication_Noauth_Union_validNoAuth", "Authentication_Noauth_Union_validToken", - // Pageable: Link-based pagination — skipped by Java, JS; - // nextLink-based pagination patterns; no ask in Azure yet (JS) - "Payload_Pageable_ServerDrivenPagination_link", - "Payload_Pageable_ServerDrivenPagination_linkString", - "Payload_Pageable_ServerDrivenPagination_nestedLink", - - // Pageable: PageSize — skipped by Java, JS; - // page-size pagination; no ask in Azure yet (JS) - "Payload_Pageable_PageSize_listWithPageSize", - "Payload_Pageable_PageSize_listWithoutContinuation", - - // Pageable: XML Pagination — skipped by Go, Java; - // XML-based pagination support incomplete in both emitters - "Payload_Pageable_XmlPagination_listWithContinuation", - "Payload_Pageable_XmlPagination_listWithNextLink", - - // Response StatusCodeRange — skipped by Go, JS; - // status code range error handling; no ask in Azure yet (JS); - // Go tracks in https://github.com/Azure/autorest.go/issues/1606 - "Response_StatusCodeRange_errorResponseStatusCodeInRange", - "Response_StatusCodeRange_errorResponseStatusCode404", - // Type File Body — skipped by Python, JS; // file upload/download with specific content types; no real case received (JS) "Type_File_Body_uploadFileSpecificContentType",