feat: Refactor Pagination: Remove Next URL Field and Update Tests #2045
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 removes the optional URL field from the PaginatedResponse model along with the associated logic for generating the next page URL. The changes include:
url
attribute and its documentation from the PaginatedResponse model inllama_stack/apis/common/responses.py
.llama_stack/distribution/server/server.py
that computed and assigned the next page URL based on request parameters. The logic to generate a next page URL whenhas_more
is true has been removed from the server route handler.tests/integration/datasets/test_datasets.py
by removing assertions related to theurl
field from the pagination response.These changes simplify the pagination implementation and align the test expectations with the current behavior of the PaginatedResponse. This refactoring closes #1847.
Please review the modifications and let me know if further adjustments are needed.
Created with Repobird.ai 📦🐦