Pagination added and search and filtering moved to backend
Build LinkLog Development Image / development-image (push) Successful in 22s
Build LinkLog Development Image / development-image (push) Successful in 22s
This commit is contained in:
@@ -300,6 +300,18 @@ Where date format is like: 2026 August 29 - 21:10
|
||||
254. In firefox the search input field is wider (at 180px) then labe search control (at 135.5px)
|
||||
255. In the toolbar switch the search and tag filter's location
|
||||
|
||||
## 2026-09-06
|
||||
|
||||
256. Use the APIs to, In the current runtime (linklog.db), add 5 random users and for each users add 500 random linklog items from different sites, each with comments and hashtags
|
||||
257. the current implementation reads the whole feed at once.
|
||||
|
||||
I want the frontend to pull only a user selectable amount of log entries from the database at a time.
|
||||
|
||||
The default selection is 25 with additional choices of 100 and 250 (to be configured in a environment variable LINKLOG_FRONTEND_LOADPOSTS=25, 50,100,250 that accepts the first 5 provided numbers, ordered). The user can select the next, or previous button or click page 1, 2, 3, ... on the bottom of the current page.
|
||||
|
||||
If the user uses the filters and/or search in the toolbox then those should limit the entries the server presents, so the filters and search are applied on the server side.
|
||||
258. Make it so that <nav id=pagination> at the bottom of the page doesn't exceed the page width and is less visually dominant
|
||||
|
||||
## Future entries
|
||||
|
||||
Append each new user prompt here with its date and preserve the chronological order.
|
||||
|
||||
Reference in New Issue
Block a user