Skip to content

Add pagination to datacontroller - #33

Closed
jeppekroghitk wants to merge 1 commit into
developfrom
feature/8191-paginated-datacontroller
Closed

jeppekroghitk wants to merge 1 commit into
developfrom
feature/8191-paginated-datacontroller

Conversation

@jeppekroghitk

@jeppekroghitk jeppekroghitk commented Sep 16, 2026

Copy link
Copy Markdown
Collaborator

Link to ticket

#8191

Description

Screenshot of the result

N/A

Checklist

  • My code is covered by test cases.
  • My code passes our test (all our tests).
  • My code passes our static analysis suite.
  • My code passes our continuous integration process.

The broker answers a list request with its first page — fifty entities —
and advertises the rest in a Link header. A map widget asks for its layer
once and draws what it gets, so the map quietly showed a fraction of the
data. Raising the limit is no way out either: the broker refuses a limit
above its own maximum with 403 TooManyResults.

A request carrying "all" is now answered with every page, followed and
merged in PagedBrokerReader. Anything else is proxied exactly as before,
so a client passing its own limit and offset keeps paging for itself.

The run gives up after a hundred pages in case a broker keeps announcing
another one, and says so in the log rather than passing off a truncated
set as the whole.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant