From d487d21eda05558538466f61a83c79cf8c947010 Mon Sep 17 00:00:00 2001 From: zrgt Date: Mon, 11 May 2026 23:48:08 +0200 Subject: [PATCH] Always include paging_metadata in paginated list responses The AAS Part 2 API spec requires GetPagedResult wrapper on every list response. The previous code omitted it when all results fit on the first page, returning a plain array that clients expecting {"result": [...], "paging_metadata": {...}} could not parse. --- server/app/interfaces/base.py | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/server/app/interfaces/base.py b/server/app/interfaces/base.py index 9e46e9dd..d3231237 100644 --- a/server/app/interfaces/base.py +++ b/server/app/interfaces/base.py @@ -240,11 +240,7 @@ def _get_slice(cls, request: Request, iterator: Iterable[T]) -> Tuple[Iterator[T paginated_slice = iter(items[:limit]) next_cursor = str(cursor + limit + 1) if has_more else None - if next_cursor is not None or cursor > 0: - # add metadata if cursor was present in request - paging_metadata = PagingMetadata(cursor=next_cursor) - else: - paging_metadata = None + paging_metadata = PagingMetadata(cursor=next_cursor) return paginated_slice, paging_metadata def handle_request(self, request: Request):