Class DeckPostListState

Posts as the discussion page asks for them: no include, so the endpoint's defaults, which extensions add to (likes, flags, mentions, ...). Core's PostListState names a few, and extensions add theirs to that list, but naming any at all turns every default off.

With no sort, the server's own order: a filter's, such as flagged posts by when they were flagged.

Reload the first page without taking the current results off screen.

refresh() clears the list and shows the loading state before it asks the API for anything, which is what you want when the reader has changed what they are looking at: the old results are wrong, and showing them would be a lie. It is the wrong shape for a background catch-up — a reconnected websocket, a regained network — where what is on screen is still valid and merely out of date. There, clearing first means the reader watches content they already had disappear behind a spinner, and loses their scroll position, to service a request they never made.

This keeps the list rendered and swaps the results in when they arrive. A failure resolves rather than rejecting: a background refresh that could not complete should leave the reader exactly as they were, not blank the page.