Repository navigation
Consolidate collection and paging checks in list-response-envelope - #6044
Mary Gao (MaryGao) wants to merge 5 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
All changed packages have been documented.
Show changes
|
📦 Package size report5 packages changed size, +18.91 KB (+0.1%) packed overall.
9 package(s) with no notable change
Packed = gzipped |
commit: |
|
You can try these changes here
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Summary
Consolidates the ARM collection-response and paging checks in the
list-response-envelopeTypeSpec linter rule.The rule reports operation-level paging and response-model envelope findings independently. It checks collection GET operations for
@list, HTTP 200 response models for exactlyvalueandnextLink, and pageable response values and TypeSpec paging metadata. Thelist-operation-missing-pageablerule ID is retired;no-query-in-collectionis not part of this PR.Swagger validators covered:
XmsPageableForListCallsGetCollectionOnlyHasValueAndNextLinkCollectionObjectPropertiesNamingFive-project comparison
Network's raw Swagger findings repeat across 19 emitted files. TypeSpec was assessed in target-only mode with HTTP-reachable alignment; project-default activation was not assessed. No project had a higher TypeSpec count in this comparison. Equal counts do not prove finding-by-finding or predicate equivalence.
CollectionObjectPropertiesNaminghad no observations in these projects.Related issues
Migration report
Rule migration report