Add test scenario for paging without nextlink/continuationToken #7493
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.
This PR adds a test scenario for a paging operation that doesn't use either nextLink or continuationToken.
The TypeSpec HTTP library allows operations to be marked with
@list
decorator and only requires that a property in the return model has the@pageItems
decorator. However, there was no test scenario to verify that this works correctly without a nextlink or continuationToken property.Changes made:
noPagination
inpackages/http-specs/specs/payload/pageable/main.tsp
that demonstrates a valid paging operation without pagination tokenspackages/http-specs/specs/payload/pageable/mockapi.ts
Code changes are minimal and follow the pattern of existing test scenarios in the codebase.
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.