[WIP] Need Spector scenario for paging without nextlink/continuationToken #7651
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.
Successfully added a missing Spector scenario for paging without nextlink or continuationToken. The current paging.md file previously only covered scenarios with continuation mechanisms, but TypeSpec supports basic
@list
operations with just@pageItems
and no continuation token.Changes Made
Added a third scenario to
packages/http-client-js/test/scenarios/http-operations/paging.md
:@list
operation with only@pageItems
decorator and no continuation mechanismThe new scenario covers:
@list op simple(@query filter: string): { @pageItems pets: Pet[]; }
PagedAsyncIterableIterator
return typenextToken: undefined
)SimpleOptions
,SimplePageSettings
,SimplePageResponse
)All existing tests continue to pass, and the new scenario generates 7 additional test cases that all pass successfully.
Fixes #6732.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.