Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use 1000-row Jitsi pages

Browse Source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Scott Idem
2026-05-06 14:21:08 -04:00
parent cd868460fe
commit 74bc3b3625
3 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
documentation/CLIENT__IDAA_and_customized_mods.md
View File

@@ -540,9 +540,12 @@ The page now reads cached `activity_log` rows from IndexedDB first, renders that
then refreshes from the API in the background. That keeps the report usable even when the network
round-trip is slow.
Both the cache path and the API refresh now page through the full matching activity-log set in
`created_on DESC` order before building the report. That avoids the old "first 500 rows" behavior
that could hide newer sessions if the log table grew large.
Both the cache path and the API refresh now page through the matching activity-log set in
`created_on DESC` order with a 1000-row page size before building the report. That avoids the old
"first 500 rows" behavior that could hide newer sessions if the log table grew large.
The report page keeps the newest session first in both the flat list and the grouped-by-room view;
grouped room rows are also sorted newest session first within each room.
### Jitsi URL Builder