fix(644): page SPA list loaders to completeness instead of inflating pageSize
Seven call sites (rerun-collections, multi-collections, library/browse) requested pageSize far above each endpoint's server-side MaxPageSize=100 clamp and took the single response page as the whole list, so rows past 100 silently vanished with no error or truncation indicator. Extract the loadAllRerunCollections pattern from SchedulesScreen (#634) into a shared, generic web/src/api/paging.ts::loadAllPages helper that pages against totalCount with an empty-page defensive break, and refactor SchedulesScreen plus the seven over-cap call sites in RerunCollectionsScreen, MultiCollectionsScreen, PlaylistsScreen, and FillerPresetsScreen to use it. Server caps are unchanged (api.search-allitems-paging precedent: client pages, server stays bounded). Document the convention in docs/spa-conventions.md §3b.
This commit is contained in:
@@ -23,6 +23,7 @@ export * from './mediaDetail';
|
||||
export * from './mediaItems';
|
||||
export * from './mediaSources';
|
||||
export * from './multiCollections';
|
||||
export * from './paging';
|
||||
export * from './pickers';
|
||||
export * from './playlists';
|
||||
export * from './playoutHistory';
|
||||
|
||||
Reference in New Issue
Block a user